)]}'
{
  "commit": "1071695f17daf050638e0bc550db647f8237c3bb",
  "tree": "4770e712c2293d0156fbb53bebc6fa059a8a99eb",
  "parents": [
    "39273b58a409cd6d65c9732bdca00bacd1626672"
  ],
  "author": {
    "name": "David Brownell",
    "email": "david-b@pacbell.net",
    "time": "Fri Feb 22 21:54:24 2008 -0800"
  },
  "committer": {
    "name": "Len Brown",
    "email": "len.brown@intel.com",
    "time": "Sat Feb 23 01:32:56 2008 -0500"
  },
  "message": "ACPI: crosslink ACPI and \"real\" device nodes\n\nAdd cross-links between ACPI device and \"real\" devices in sysfs,\nexposing otherwise-hidden interrelationships between the various\ndevice nodes for ACPI stuff.  As a representative example, one\nhardware device is exposed as two logical devices (PNP and ACPI):\n\n  .../pnp0/00:06/\n  .../LNXSYSTM:00/device:00/PNP0A03:00/device:15/PNP0B00:00/\n\nThe PNP device gets a \"firmware_node\" link pointing to the ACPI device,\nand is what a Linux device driver binds to.  The ACPI device has instead\na \"physical_node\" link pointing back to the PNP device.  Other firmware\nframeworks, like OpenFirmware, could do the same thing to couple their\nfirmware tables to the rest of the system.\n\n(Based on a patch from Zhang Rui.  This version is modified to not\ndepend on the patch makig ACPI initialize driver model wakeup flags.)\n\nSigned-off-by: David Brownell \u003cdbrownell@users.sourceforge.net\u003e\nCc: Zhang Rui \u003crui.zhang@intel.com\u003e\nSigned-off-by: Len Brown \u003clen.brown@intel.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "eda0978b57c6946b9580ab24869794a2bc14b2bd",
      "old_mode": 33188,
      "old_path": "drivers/acpi/glue.c",
      "new_id": "06f8634fe58b192498ad73c5e4d4a4e715b01cf3",
      "new_mode": 33188,
      "new_path": "drivers/acpi/glue.c"
    }
  ]
}