)]}'
{
  "commit": "b46f205da647608a4064ce0a0acb07a8c74c6f23",
  "tree": "c1a21b678e00388e81ef64d97325d0de09c9abae",
  "parents": [
    "238c6d54830c624f34ac9cf123ac04aebfca5013"
  ],
  "author": {
    "name": "Bartlomiej Zolnierkiewicz",
    "email": "bzolnier@gmail.com",
    "time": "Tue Jan 06 17:20:47 2009 +0100"
  },
  "committer": {
    "name": "Bartlomiej Zolnierkiewicz",
    "email": "bzolnier@gmail.com",
    "time": "Tue Jan 06 17:20:47 2009 +0100"
  },
  "message": "ide: fix LOCKDEP warning\n\ncommit 295f00042aaf6b553b5f37348f89bab463d4a469 (\"ide: don\u0027t execute\nthe next queued command from the hard-IRQ context\") overlooked that\nide_do_drive_cmd() (used for REQUEST SENSE command handling) may still\ninvoke do_ide_request() (-\u003erequest_fn) in the hard-IRQ context through\nblk_start_queueing().  This resulted in a LOCKDEP warning after commit\nb599bc7a1199419e122cb2e9ec6b0fa2cfbbc17b (\"ide: use per-device request\nqueue locks (v2)\").\n\nSince calling blk_start_queuing() in ide_do_drive_cmd() doesn\u0027t make\nmuch sense as the port is already marked as busy (so the execution of\nthe new command will be deferred anyway) then just remove it fixing\nLOCKDEP warning and saving some CPU cycles at the same time.\n\nReported-and-tested-by: Larry Finger \u003cLarry.Finger@lwfinger.net\u003e\nReported-by: Grissiom \u003cchaos.proton@gmail.com\u003e\nSigned-off-by: Bartlomiej Zolnierkiewicz \u003cbzolnier@gmail.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "1c36a8e83d36000b1585080093e40a28b6681963",
      "old_mode": 33188,
      "old_path": "drivers/ide/ide-io.c",
      "new_id": "c3cbe5a1e307631e4685eb6852bb7fea606cea79",
      "new_mode": 33188,
      "new_path": "drivers/ide/ide-io.c"
    }
  ]
}