)]}'
{
  "commit": "96c87607ac8f9b0e641d11ba6e57f8ec0214ea1c",
  "tree": "d8a7d538b2bd05b5ee2957828563b31cf7db8540",
  "parents": [
    "77fba13ccc3a2a3db100892a4a6cc5e2f8290cc7"
  ],
  "author": {
    "name": "Henrique de Moraes Holschuh",
    "email": "hmh@hmh.eng.br",
    "time": "Sat Aug 02 15:11:00 2008 -0300"
  },
  "committer": {
    "name": "John W. Linville",
    "email": "linville@tuxdriver.com",
    "time": "Fri Aug 22 16:29:57 2008 -0400"
  },
  "message": "rfkill: introduce RFKILL_STATE_MAX\n\nWhile it is interesting to not add last-enum-markers because it allows gcc\nto warn us of switch() statements missing a valid state, we really should\nbe handling memory corruption on a rfkill state with default clauses,\nanyway.\n\nSo add RFKILL_STATE_MAX and use it where applicable.  It makes for safer\ncode in the long run.\n\nSigned-off-by: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e\nAcked-by: Ivo van Doorn \u003cIvDoorn@gmail.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "e92d8e94bb888bbacc17641ad1f78c808aaa1b3c",
      "old_mode": 33188,
      "old_path": "include/linux/rfkill.h",
      "new_id": "4cd64b0d9825a6b2bbe33b9a584b1233a03ac54d",
      "new_mode": 33188,
      "new_path": "include/linux/rfkill.h"
    },
    {
      "type": "modify",
      "old_id": "fae7ffade9c93acc02f2441cd7d38e5ca3c00525",
      "old_mode": 33188,
      "old_path": "net/rfkill/rfkill.c",
      "new_id": "47e0b2d232e30c120121e85e10e88902f86f4e52",
      "new_mode": 33188,
      "new_path": "net/rfkill/rfkill.c"
    }
  ]
}