)]}'
{
  "log": [
    {
      "commit": "19d337dff95cbf76edd3ad95c0cee2732c3e1ec5",
      "tree": "33326eeb09cb9664cc8427a5dc7cd2b08b5a57c3",
      "parents": [
        "0f6399c4c525b518644a9b09f8d6fb125a418c4d"
      ],
      "author": {
        "name": "Johannes Berg",
        "email": "johannes@sipsolutions.net",
        "time": "Tue Jun 02 13:01:37 2009 +0200"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Wed Jun 03 14:06:13 2009 -0400"
      },
      "message": "rfkill: rewrite\n\nThis patch completely rewrites the rfkill core to address\nthe following deficiencies:\n\n * all rfkill drivers need to implement polling where necessary\n   rather than having one central implementation\n\n * updating the rfkill state cannot be done from arbitrary\n   contexts, forcing drivers to use schedule_work and requiring\n   lots of code\n\n * rfkill drivers need to keep track of soft/hard blocked\n   internally -- the core should do this\n\n * the rfkill API has many unexpected quirks, for example being\n   asymmetric wrt. alloc/free and register/unregister\n\n * rfkill can call back into a driver from within a function the\n   driver called -- this is prone to deadlocks and generally\n   should be avoided\n\n * rfkill-input pointlessly is a separate module\n\n * drivers need to #ifdef rfkill functions (unless they want to\n   depend on or select RFKILL) -- rfkill should provide inlines\n   that do nothing if it isn\u0027t compiled in\n\n * the rfkill structure is not opaque -- drivers need to initialise\n   it correctly (lots of sanity checking code required) -- instead\n   force drivers to pass the right variables to rfkill_alloc()\n\n * the documentation is hard to read because it always assumes the\n   reader is completely clueless and contains way TOO MANY CAPS\n\n * the rfkill code needlessly uses a lot of locks and atomic\n   operations in locked sections\n\n * fix LED trigger to actually change the LED when the radio state\n   changes -- this wasn\u0027t done before\n\nTested-by: Alan Jenkins \u003calan-jenkins@tuffmail.co.uk\u003e\nSigned-off-by: Henrique de Moraes Holschuh \u003chmh@hmh.eng.br\u003e [thinkpad]\nSigned-off-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    },
    {
      "commit": "2a4d71d69f97cef48da969ab917b55e0193ed9ec",
      "tree": "d25057774312c18d33f6682714746a3b12b7278d",
      "parents": [
        "c17931c52ec6b1af710185986e10c344039edeb7"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Fri Jan 09 07:34:00 2009 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Sun Jan 11 00:06:32 2009 -0800"
      },
      "message": "wimax: fix typo in kernel-doc for debugfs_dentry in struct wimax_dev\n\nThe kernel-doc was referring to member @debufs_dentry instead of\n@debugfs_dentry.\n\nReported by Randy Dunlap http://marc.info/?l\u003dlinux-netdev\u0026m\u003d123147942302885\u0026w\u003d2\n\nAs well, escape the colon in the field\u0027s text description, as it is\ncausing the generated text to be erraticly broken up (with paragraphs\nmoved down). Could not find a reason why it is happening so, even when\nother field descriptions use colons and work as expected.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "56cf391a9462a4897ea660a6af3662dda5ae8c84",
      "tree": "401a292acb65581396428c2f48cf464646989162",
      "parents": [
        "8cb89571bd66fec6a71d8a2b1de2262722dfbb8d"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Thu Jan 08 12:56:57 2009 -0800"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Thu Jan 08 12:56:57 2009 -0800"
      },
      "message": "wimax: fix kernel-doc for debufs_dentry member of struct wimax_dev\n\nReported by Randy Dunlap from a warning in the v2.6.29 merge window\ntree as of 2009/1/8.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "ace22f0881e1333d0c55ddf484e5352fe03a806a",
      "tree": "e604b974810263cfb6721fd4846bf61888b6b518",
      "parents": [
        "0d695913b0016b362a84a8bb6d6e28f8d90a70e2"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Sat Dec 20 16:57:33 2008 -0800"
      },
      "committer": {
        "name": "Greg Kroah-Hartman",
        "email": "gregkh@suse.de",
        "time": "Wed Jan 07 10:00:16 2009 -0800"
      },
      "message": "wimax: headers for kernel API and user space interaction\n\nDefinitions for the user/kernel API protocol through generic\nnetlink. User space can copy it verbatim and use it.\n\nKernel API definition declares the main data types and calls for the\ndrivers to integrate into the WiMAX stack. Provides usage\ndocumentation.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n"
    }
  ]
}