)]}'
{
  "commit": "bf3204cbff7d2606e758afb0994e8da6ae1c6c26",
  "tree": "01951b829d2af6a52b82bec35cc05261dcf77fe2",
  "parents": [
    "558a5e296a02266ef43d6e933ee35df9976de987"
  ],
  "author": {
    "name": "Dmitry Torokhov",
    "email": "dmitry.torokhov@gmail.com",
    "time": "Fri Nov 06 21:39:07 2009 -0800"
  },
  "committer": {
    "name": "Dmitry Torokhov",
    "email": "dmitry.torokhov@gmail.com",
    "time": "Tue Nov 10 21:13:32 2009 -0800"
  },
  "message": "Input: fix locking in memoryless force-feedback devices\n\nNow that input core acquires dev-\u003eevent_lock spinlock and disables\ninterrupts when propagating input events, using spin_lock_bh() in\nff-memless driver is not allowed. Actually, the timer_lock itself\nis not needed anymore, we should simply use dev-\u003eevent_lock\nas well.\n\nAlso do a small cleanup in force-feedback core.\n\nReported-by: kerneloops.org\nReported-by: http://www.kerneloops.org/searchweek.php?search\u003dml_ff_set_gain\nReported-by: Arjan van de Ven \u003carjan@linux.intel.com\u003e\nSigned-off-by: Dmitry Torokhov \u003cdtor@mail.ru\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "72c63e5dd630709ddffccf8dc945147857bf41ba",
      "old_mode": 33188,
      "old_path": "drivers/input/ff-core.c",
      "new_id": "38df81fcdc3a90bdb4f812a02a4d064e6d657f2d",
      "new_mode": 33188,
      "new_path": "drivers/input/ff-core.c"
    },
    {
      "type": "modify",
      "old_id": "2d1415e1683467ae55de53ba3fb273996ba7a795",
      "old_mode": 33188,
      "old_path": "drivers/input/ff-memless.c",
      "new_id": "b483b2995fa9918ad9cec432b37f0248517c45af",
      "new_mode": 33188,
      "new_path": "drivers/input/ff-memless.c"
    },
    {
      "type": "modify",
      "old_id": "0ccfc30cd40f7696e0b9e863272f82fb8e42e0f0",
      "old_mode": 33188,
      "old_path": "include/linux/input.h",
      "new_id": "c2b1a7d244d918f9127aaf557b6127a2b12486c7",
      "new_mode": 33188,
      "new_path": "include/linux/input.h"
    }
  ]
}