)]}'
{
  "commit": "8619f9b5bbcc5d1b1f9ce44d1beeb6c991782ea6",
  "tree": "e41ba74faf1740a4a1dfcf01d1f23b5479172845",
  "parents": [
    "28be787b59403ca877de2d4b55cc8487d67d4b0e"
  ],
  "author": {
    "name": "Linus Torvalds",
    "email": "torvalds@linux-foundation.org",
    "time": "Wed Sep 04 05:02:55 2019 +0000"
  },
  "committer": {
    "name": "Johannes Weiner",
    "email": "hannes@cmpxchg.org",
    "time": "Wed Sep 04 05:02:55 2019 +0000"
  },
  "message": "pci: test for unexpectedly disabled bridges\n\nThe all-ones value is not just a \"device didn\u0027t exist\" case, it\u0027s also\npotentially a quite valid value, so not restoring it would be wrong.\n\nWhat *would* be interesting is to hear where the bad values came from in\nthe first place.  It sounds like the device state is saved after the PCI\nbus controller in front of the device has been crapped on, resulting in the\nPCI config cycles never reaching the device at all.\n\nSomething along this patch (together with suspend/resume debugging output)\nmigth help pinpoint it.  But it really sounds like something totally\nbrokenly turned off the PCI bridge (some ACPI shutdown crud?  I wouldn\u0027t be\nentirely surprised)\n\nCc: Greg KH \u003cgreg@kroah.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "484e3534956527cd4b6f7ca30ece12b9df6f1074",
      "old_mode": 33188,
      "old_path": "drivers/pci/pci.c",
      "new_id": "91536929abcc1851bac5fa3bd9d4153943b73347",
      "new_mode": 33188,
      "new_path": "drivers/pci/pci.c"
    }
  ]
}