)]}'
{
  "commit": "4a9d916717de0aab4313d43817164577255242fb",
  "tree": "504d7b6df2e0998eb2f4df3c6e4a1939d97b1598",
  "parents": [
    "964d2777438bf7687324243d38ade538d9bbfe3c"
  ],
  "author": {
    "name": "Jonathan McDowell",
    "email": "noodles@earth.li",
    "time": "Thu Oct 30 22:46:48 2008 +0000"
  },
  "committer": {
    "name": "John W. Linville",
    "email": "linville@tuxdriver.com",
    "time": "Thu Nov 06 16:37:09 2008 -0500"
  },
  "message": "Fix logic error in rfkill_check_duplicity\n\n\u003e I\u0027ll have a prod at why the [hso] rfkill stuff isn\u0027t working next\n\nOk, I believe this is due to the addition of rfkill_check_duplicity in\nrfkill and the fact that test_bit actually returns a negative value\nrather than the postive one expected (which is of course equally true).\nSo when the second WLAN device (the hso device, with the EEE PC WLAN\nbeing the first) comes along rfkill_check_duplicity returns a negative\nvalue and so rfkill_register returns an error. Patch below fixes this\nfor me.\n\nSigned-Off-By: Jonathan McDowell \u003cnoodles@earth.li\u003e\nAcked-by: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "f949a482b0078b904d88b655da399d8706a48ca8",
      "old_mode": 33188,
      "old_path": "net/rfkill/rfkill.c",
      "new_id": "25ba3bd57e66405e64adef4455b66614fd273ea6",
      "new_mode": 33188,
      "new_path": "net/rfkill/rfkill.c"
    }
  ]
}