)]}'
{
  "log": [
    {
      "commit": "9306102ea5696a3815f8d24ac0c0fbd1e19be7d3",
      "tree": "4dd9e512203616345d43f825ac808b0be1901bea",
      "parents": [
        "3c57601d0a1993cfc12a27cc6652b750bb44c523"
      ],
      "author": {
        "name": "Emmanuel Grumbach",
        "email": "emmanuel.grumbach@intel.com",
        "time": "Thu May 29 16:35:23 2008 +0800"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Tue Jun 03 15:00:26 2008 -0400"
      },
      "message": "mac80211: allow disable FAT in specific configurations\n\nThis patch allows to disable FAT channel in specific configurations.\n\nFor example the configuration (8, +1), (primary channel 8, extension\nchannel 12) isn\u0027t permitted in U.S., but (8, -1), (primary channel 8,\nextension channel 4) is. When FAT channel configuration is not\npermitted, FAT channel should be reported as not supported in the\ncapabilities of the HT IE in association request. And sssociation is\nperformed on 20Mhz channel.\n\nSigned-off-by: Emmanuel Grumbach \u003cemmanuel.grumbach@intel.com\u003e\nSigned-off-by: Tomas Winkler \u003ctomas.winkler@intel.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    },
    {
      "commit": "6c507cd0400cb51dd2ee251c1b8756b9375a1128",
      "tree": "2b3d44a34e2c3d2ba1e9e0c557fb0730227f5bb4",
      "parents": [
        "7d5796118353cd45e9e301fdf3ff99fdec5390e9"
      ],
      "author": {
        "name": "Johannes Berg",
        "email": "johannes@sipsolutions.net",
        "time": "Wed Mar 26 14:14:55 2008 +0100"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Thu Mar 27 16:03:20 2008 -0400"
      },
      "message": "cfg80211: don\u0027t export ieee80211_get_channel\n\nThis patch makes ieee80211_get_channel a static inline defined in\ncfg80211\u0027s header file which simply calls __ieee80211_get_channel\nto avoid symbol clashes with the ieee80211 code.\n\nThe problem was pointed out by David Miller, thanks!\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nCc: David Miller \u003cdavem@davemloft.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    },
    {
      "commit": "906c730a2db950b7bce4ef17d65399acd791c360",
      "tree": "75df7353a1407fdcdca45e6f289ab0f25b2361af",
      "parents": [
        "857485c0c46ceee5c658c1761bba4d9a5ddf433f"
      ],
      "author": {
        "name": "Johannes Berg",
        "email": "johannes@sipsolutions.net",
        "time": "Sun Mar 16 18:34:33 2008 +0100"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Tue Mar 25 16:41:55 2008 -0400"
      },
      "message": "wireless: add wiphy channel freq to channel struct lookup helper\n\nAdd ieee80211_get_channel() which gets you a channel struct for a\nspecific wiphy if that channel is present in that wiphy.\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    },
    {
      "commit": "8318d78a44d49ac1edf2bdec7299de3617c4232e",
      "tree": "d434634418edd7399737801615d247be06616fdd",
      "parents": [
        "10b6b80145cc93887dd8aab99bfffa375e9add31"
      ],
      "author": {
        "name": "Johannes Berg",
        "email": "johannes@sipsolutions.net",
        "time": "Thu Jan 24 19:38:38 2008 +0100"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Fri Feb 29 15:19:32 2008 -0500"
      },
      "message": "cfg80211 API for channels/bitrates, mac80211 and driver conversion\n\nThis patch creates new cfg80211 wiphy API for channel and bitrate\nregistration and converts mac80211 and drivers to the new API. The\nold mac80211 API is completely ripped out. All drivers (except ath5k)\nare updated to the new API, in many cases I expect that optimisations\ncan be done.\n\nAlong with the regulatory code I\u0027ve also ripped out the\nIEEE80211_HW_DEFAULT_REG_DOMAIN_CONFIGURED flag, I believe it to be\nunnecessary if the hardware simply gives us whatever channels it wants\nto support and we then enable/disable them as required, which is pretty\nmuch required for travelling.\n\nAdditionally, the patch adds proper \"basic\" rate handling for STA\nmode interface, AP mode interface will have to have new API added\nto allow userspace to set the basic rate set, currently it\u0027ll be\nempty... However, the basic rate handling will need to be moved to\nthe BSS conf stuff.\n\nI do expect there to be bugs in this, especially wrt. transmit\npower handling where I\u0027m basically clueless about how it should work.\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    },
    {
      "commit": "704232c2718c9d4b3375ec15a14fc0397970c449",
      "tree": "6ffaa759ebaee36c4242bff6b7630f148efcaea3",
      "parents": [
        "2a5e1c0eb9efe26eed1dd072fe08de5797a7efd5"
      ],
      "author": {
        "name": "Johannes Berg",
        "email": "johannes@sipsolutions.net",
        "time": "Mon Apr 23 12:20:05 2007 -0700"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@sunset.davemloft.net",
        "time": "Wed Apr 25 22:29:41 2007 -0700"
      },
      "message": "[WIRELESS] cfg80211: New wireless config infrastructure.\n\nThis patch creates the core cfg80211 code along with some sysfs bits.\nThis is a stripped down version to allow mac80211 to function, but\ndoesn\u0027t include any configuration yet except for creating and removing\nvirtual interfaces.\n\nThis patch includes the nl80211 header file but it only contains the\ninterface types which the cfg80211 interface for creating virtual\ninterfaces relies on.\n\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    }
  ]
}