)]}'
{
  "log": [
    {
      "commit": "6039f6d23fe792d615da5449e9fa1c6b43caacf6",
      "tree": "af94d1ad78ce1e82d76328ea9a67b351f0a9174b",
      "parents": [
        "a299542e97ec1939fdca7db6d3d82c0aa9bf8b9a"
      ],
      "author": {
        "name": "Jouni Malinen",
        "email": "jouni.malinen@atheros.com",
        "time": "Thu Mar 19 13:39:21 2009 +0200"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Fri Mar 27 20:13:02 2009 -0400"
      },
      "message": "nl80211: Event notifications for MLME events\n\nAdd new nl80211 event notifications (and a new multicast group, \"mlme\")\nfor informing user space about received and processed Authentication,\n(Re)Association Response, Deauthentication, and Disassociation frames in\nstation and IBSS modes (i.e., MLME SAP interface primitives\nMLME-AUTHENTICATE.confirm, MLME-ASSOCIATE.confirm,\nMLME-REASSOCIATE.confirm, MLME-DEAUTHENTICATE.indicate, and\nMLME-DISASSOCIATE.indication). The event data is encapsulated as the 802.11\nmanagement frame since we already have the frame in that format and it\nincludes all the needed information.\n\nThis is the initial step in providing MLME SAP interface for\nauthentication and association with nl80211. In other words, kernel code\nwill act as the MLME and a user space application can control it as the\nSME.\n\nSigned-off-by: Jouni Malinen \u003cj@w1.fi\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    }
  ]
}