)]}'
{
  "commit": "2449e06a5696b7af1c8a369b04c97f3b139cf3bb",
  "tree": "22ee432f869df8c703fb25035e06d4e92d56be7f",
  "parents": [
    "3095fc0c9772b4afb3c81f76664f341ef716d380"
  ],
  "author": {
    "name": "Shaohua Li",
    "email": "shaohua.li@intel.com",
    "time": "Fri Oct 20 14:45:32 2006 -0700"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Fri Oct 27 11:20:33 2006 -0700"
  },
  "message": "PCI: reset pci device state to unknown state for resume\n\nConsidering below scenario:\n1.Unload a PCI device\u0027s driver, the device -\u003ecurrent remains in PCI_D0.\n2.Do suspend/resume circle. After that, BIOS puts the device to D3.\n3.Reload the device driver. The calling pci_set_power_state in the\ndriver can\u0027t change the state to D0, as set_power_state thinks the\ndevice is already in D0.\n\nA bug is reported at http://bugzilla.kernel.org/show_bug.cgi?id\u003d6024\nPat attached a patch at\nhttp://marc.theaimsgroup.com/?l\u003dlinux-pci\u0026m\u003d114049761428561\u0026w\u003d2 for this\nissue, but it\u0027s lost. As pci_set_power_state can handle D3 -\u003e D0\ncorrectly (restore config space), I simplified Patrick\u0027s patch.\n\nSigned-off-by: Shaohua Li \u003cshaohua.li@intel.com\u003e\nCc: Patrick Mochel \u003cmochel@digitalimplant.org\u003e\nSigned-off-by: Andrew Morton \u003cakpm@osdl.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "b1c0c707d96ccc6e713042b1d67167609199c723",
      "old_mode": 33188,
      "old_path": "drivers/pci/pci-driver.c",
      "new_id": "194f1d21d3d784d3ce73301acf42ff5c38240e32",
      "new_mode": 33188,
      "new_path": "drivers/pci/pci-driver.c"
    }
  ]
}