)]}'
{
  "commit": "bb3bf7052de520f2d21a1275e95fac7a84d89e4c",
  "tree": "791d90c55d835ef7f81c6d7fe98efcbbf6872869",
  "parents": [
    "d5f546d834ddc44539651e9955eb3577b0a3eb8b"
  ],
  "author": {
    "name": "Paul E. McKenney",
    "email": "paul.mckenney@linaro.org",
    "time": "Fri Nov 04 13:24:07 2011 -0700"
  },
  "committer": {
    "name": "Paul E. McKenney",
    "email": "paulmck@linux.vnet.ibm.com",
    "time": "Sun Dec 11 10:31:47 2011 -0800"
  },
  "message": "rcu: Control rcutorture startup from kernel boot parameters\n\nCurrently, if rcutorture is built into the kernel, it must be manually\nstarted or started from an init script.  This is inconvenient for\nautomated KVM testing, where it is good to be able to fully control\nrcutorture execution from the kernel parameters.  This patch therefore\nadds a module parameter named \"rcutorture_runnable\" that defaults\nto zero (\"don\u0027t start automatically\"), but which can be set to one\nto cause rcutorture to start up immediately during boot.\n\nSigned-off-by: Paul E. McKenney \u003cpaul.mckenney@linaro.org\u003e\nSigned-off-by: Paul E. McKenney \u003cpaulmck@linux.vnet.ibm.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ce84091291b543a56444e5b6cdc166e8b54f1338",
      "old_mode": 33188,
      "old_path": "kernel/rcutorture.c",
      "new_id": "eed9f46eb0a5c1680cbd3c6ba56e0bb6f01b3047",
      "new_mode": 33188,
      "new_path": "kernel/rcutorture.c"
    }
  ]
}