)]}'
{
  "commit": "71f78afd67ca51d3656ba45aea293d6e2a27c8bc",
  "tree": "f6ac9e2aab523d9fdf2918691209db0c7dcad589",
  "parents": [
    "d48e470f76887d0befe025049158aeb6c1219d71"
  ],
  "author": {
    "name": "Inaky Perez-Gonzalez",
    "email": "inaky@linux.intel.com",
    "time": "Thu Jan 08 11:07:36 2009 -0800"
  },
  "committer": {
    "name": "David S. Miller",
    "email": "davem@davemloft.net",
    "time": "Thu Jan 08 11:07:36 2009 -0800"
  },
  "message": "wimax: fix kconfig interactions with rfkill and input layers\n\nWiMAX can work without RFKILL, but it was missing a check to make sure\nRFKILL is not being made a module with wimax compiled into the\nkernel. This caused failed builds in s390, where CONFIG_INPUT is\nalways off.\n\nWhen RFKILL is enabled, the code uses the input layer to report\nhardware switch changes; thus, if RFKILL is enabled, INPUT has to be\ntoo. It also needs to display some message when INPUT is disabled that\nexplains why WiMAX is not selectable.\n\n(issues found by Randy Dunlap in the linux-next tree).\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0bdbb6928205227e79c681cd9d8a1ee498e21705",
      "old_mode": 33188,
      "old_path": "net/wimax/Kconfig",
      "new_id": "18495cdcd10de2e356a76cbafc1351d516c70633",
      "new_mode": 33188,
      "new_path": "net/wimax/Kconfig"
    }
  ]
}
