)]}'
{
  "commit": "294196ab22c91da974ba1f40d0a7cdcb0b3e6bc3",
  "tree": "10301cf8cff8c6bfa1db351f5570b9b182ad8499",
  "parents": [
    "768777ea1118f6ff3f1a013557e7bc4f5d2683a4"
  ],
  "author": {
    "name": "Luis R. Rodriguez",
    "email": "lrodriguez@atheros.com",
    "time": "Sat May 02 00:37:20 2009 -0400"
  },
  "committer": {
    "name": "John W. Linville",
    "email": "linville@tuxdriver.com",
    "time": "Wed May 20 14:46:23 2009 -0400"
  },
  "message": "cfg80211: check allowed channel type upon userspace requests\n\nThanks to nl80211 userspace can be very specific upon device\nconfiguration. Before processing the request for the new HT40\nchannel types (HT40- or HT40+) we need to ensure we can use them\nregulatory-wise. This wasn\u0027t required with wireless extensions as\nspecifying the channel type wasn\u0027t not available and configuration\nwas done towards the end implicitly upon association or reception\nof beacons from the AP. For the new nl80211 we have to check this\nwhen configuring the interfaces explicitly.\n\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": "ade40d503bf01ae400539fe57d7a396aa2eb3342",
      "old_mode": 33188,
      "old_path": "net/wireless/nl80211.c",
      "new_id": "0e22b5f5880fef771fb01ff66c20b7c2a08689fa",
      "new_mode": 33188,
      "new_path": "net/wireless/nl80211.c"
    }
  ]
}