)]}'
{
  "commit": "82bb67f2c1f9ef438c56ac24e7dca027fe7289b5",
  "tree": "e0531466b19295129692da81bdff3538ab3621b3",
  "parents": [
    "8b4b8a24e4e49dc9fe36d4d079f6d2c23f942b03"
  ],
  "author": {
    "name": "David Brownell",
    "email": "david-b@pacbell.net",
    "time": "Mon Aug 14 23:11:04 2006 -0700"
  },
  "committer": {
    "name": "Greg Kroah-Hartman",
    "email": "gregkh@suse.de",
    "time": "Mon Sep 25 21:08:37 2006 -0700"
  },
  "message": "PM: define PM_EVENT_PRETHAW\n\nThis adds a new pm_message_t event type to use when preparing to restore a\nswsusp snapshot.  Devices that have been initialized by Linux after resume\n(rather than left in power-up-reset state) may need to be reset; this new\nevent type give drivers the chance to do that.\n\nThe drivers that will care about this are those which understand more hardware\nstates than just \"on\" and \"reset\", relying on hardware state during resume()\nmethods to be either the state left by the preceding suspend(), or a\npower-lost reset.  The best current example of this class of drivers are USB\nhost controller drivers, which currently do not work through swsusp when\nthey\u0027re statically linked.\n\nWhen the swsusp freeze/thaw mechanism kicks in, a troublesome third state\ncould exist: one state set up by a different kernel instance, before a\nsnapshot image is resumed.  This mechanism lets drivers prevent that state.\n\nSigned-off-by: David Brownell \u003cdbrownell@users.sourceforge.net\u003e\nCc: \"Rafael J. Wysocki\" \u003crjw@sisk.pl\u003e\nCc: Pavel Machek \u003cpavel@ucw.cz\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": "096fb6f754cf2ae6320e48a1a68f1f452f7ba6fd",
      "old_mode": 33188,
      "old_path": "include/linux/pm.h",
      "new_id": "6b27e07aef199531387dc65bcc400c9157c79a9d",
      "new_mode": 33188,
      "new_path": "include/linux/pm.h"
    }
  ]
}