)]}'
{
  "commit": "77fba13ccc3a2a3db100892a4a6cc5e2f8290cc7",
  "tree": "326794992d81c2372f6a639df798e3361dcb4610",
  "parents": [
    "9961920199ec88d6b581d3e38502088935925c04"
  ],
  "author": {
    "name": "Henrique de Moraes Holschuh",
    "email": "hmh@hmh.eng.br",
    "time": "Sat Aug 02 15:10:59 2008 -0300"
  },
  "committer": {
    "name": "John W. Linville",
    "email": "linville@tuxdriver.com",
    "time": "Fri Aug 22 16:29:57 2008 -0400"
  },
  "message": "rfkill: add __must_check annotations\n\nrfkill is not a small, mere detail in wireless support.  Once it starts\nsupporting rfkill and users start counting on that support, a wireless\ndevice is at risk of operating in dangerous conditions should rfkill\nsupport fail to properly activate.\n\nTherefore, add the required __must_check annotations on some key functions\nof the rfkill API, for which the wireless drivers absolutely MUST handle\nthe failure mode safely in order to avoid a potentially dangerous situation\nwhere the wireless transmitter is left enabled when the user don\u0027t want it\nto.\n\nSigned-off-by: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e\nAcked-by: Ivo van Doorn \u003cIvDoorn@gmail.com\u003e\nCc: Matthew Garrett \u003cmjg@redhat.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "aa3c7d5852f6c1b18bc9c306447c60222c97bf0d",
      "old_mode": 33188,
      "old_path": "include/linux/rfkill.h",
      "new_id": "e92d8e94bb888bbacc17641ad1f78c808aaa1b3c",
      "new_mode": 33188,
      "new_path": "include/linux/rfkill.h"
    },
    {
      "type": "modify",
      "old_id": "b995fa32cf84feefff2f07d006d4e4e70e544f58",
      "old_mode": 33188,
      "old_path": "net/rfkill/rfkill.c",
      "new_id": "fae7ffade9c93acc02f2441cd7d38e5ca3c00525",
      "new_mode": 33188,
      "new_path": "net/rfkill/rfkill.c"
    }
  ]
}