)]}'
{
  "commit": "774b06780be20d07c5459becd6495c04523a93a2",
  "tree": "fc91522465fd85a9e48f6736545214e2fd60eca8",
  "parents": [
    "40969c7dd6298718820e0818b5b5acef7b24923d"
  ],
  "author": {
    "name": "Corentin Chary",
    "email": "corentin.chary@gmail.com",
    "time": "Thu Dec 15 08:27:34 2011 +0100"
  },
  "committer": {
    "name": "Matthew Garrett",
    "email": "mjg@redhat.com",
    "time": "Tue Mar 20 12:02:16 2012 -0400"
  },
  "message": "asus-laptop: control how BLED and WLED should be exposed\n\nLet the user tells if BLED and WLED should be exposed as led or\nrfkill (the old sysfs are still here, but this adds a standard\ninterface to control the device).\n\nFor example on my A6JC, with WAPF\u003d1, I would do:\n\n$ modprobe asus-laptop wled_type\u003dled bluetooth_type\u003drfkill\n\nThere is still no known way to automatically guess what BLED\nand WLED methods will control, it\u0027s why user information is needed.\n\nA userspace database could do that automatically, and maybe some DMI\nmatching in the driver.\n\nSigned-off-by: Corentin Chary \u003ccorentin.chary@gmail.com\u003e\nSigned-off-by: Matthew Garrett \u003cmjg@redhat.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "db32d0337a7ce509d3ad88301779390b96056da2",
      "old_mode": 33188,
      "old_path": "drivers/platform/x86/asus-laptop.c",
      "new_id": "e416867c07255fd0961ea5cd614b0fe9797405c4",
      "new_mode": 33188,
      "new_path": "drivers/platform/x86/asus-laptop.c"
    }
  ]
}