)]}'
{
  "commit": "9236d838c920e90708570d9bbd7bb82d30a38130",
  "tree": "ee2d9ae6b4f82efe3b28e33abebec96b7e136141",
  "parents": [
    "b5261cf4f3860bd772346a3e692683b6144dd44c"
  ],
  "author": {
    "name": "Luis R. Rodriguez",
    "email": "lrodriguez@atheros.com",
    "time": "Fri Nov 12 16:31:23 2010 -0800"
  },
  "committer": {
    "name": "John W. Linville",
    "email": "linville@tuxdriver.com",
    "time": "Tue Nov 16 15:59:39 2010 -0500"
  },
  "message": "cfg80211: fix extension channel checks to initiate communication\n\nWhen operating in a mode that initiates communication and using\nHT40 we should fail if we cannot use both primary and secondary\nchannels to initiate communication. Our current ht40 allowmap\nonly covers STA mode of operation, for beaconing modes we need\na check on the fly as the mode of operation is dynamic and\nthere other flags other than disable which we should read\nto check if we can initiate communication.\n\nDo not allow for initiating communication if our secondary HT40\nchannel has is either disabled, has a passive scan flag, a\nno-ibss flag or is a radar channel. Userspace now has similar\nchecks but this is also needed in-kernel.\n\nReported-by: Jouni Malinen \u003cjouni.malinen@atheros.com\u003e\nCc: stable@kernel.org\nSigned-off-by: Luis R. Rodriguez \u003clrodriguez@atheros.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "d0c92dddb26bddb5b3d55a82ebf39fa8917e446c",
      "old_mode": 33188,
      "old_path": "net/wireless/chan.c",
      "new_id": "c8d190d911e46984b5eb43ebf3f625e035a32bed",
      "new_mode": 33188,
      "new_path": "net/wireless/chan.c"
    }
  ]
}