)]}'
{
  "log": [
    {
      "commit": "7176ba23f8b589b1df3229574ff46fb904ce9ec5",
      "tree": "e0811eed20f2f636c217f719862a63b6652543b8",
      "parents": [
        "c6820f1e6c8273ca4b8f94c2354193d19e1a5c47"
      ],
      "author": {
        "name": "Rhyland Klein",
        "email": "rklein@nvidia.com",
        "time": "Mon May 16 14:41:48 2011 -0700"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Thu May 19 13:53:54 2011 -0400"
      },
      "message": "net: rfkill: add generic gpio rfkill driver\n\nThis adds a new generic gpio rfkill driver to support rfkill switches\nwhich are controlled by gpios. The driver also supports passing in\ndata about the clock for the radio, so that when rfkill is blocking,\nit can disable the clock.\n\nThis driver assumes platform data is passed from the board files to\nconfigure it for specific devices.\n\nOriginal-patch-by: Anantha Idapalapati \u003caidapalapati@nvidia.com\u003e\nSigned-off-by: Rhyland Klein \u003crklein@nvidia.com\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    },
    {
      "commit": "cbc6a6ed0900aed789b5ca77192845f2f987af70",
      "tree": "d7aa6e267e34417a857121de210ffd47f8e0eb2a",
      "parents": [
        "bb411b4db2767cfd4a99b3328da843ce4ea1596a"
      ],
      "author": {
        "name": "Antonio Ospite",
        "email": "ospite@studenti.unina.it",
        "time": "Wed Apr 13 21:40:45 2011 +0200"
      },
      "committer": {
        "name": "John W. Linville",
        "email": "linville@tuxdriver.com",
        "time": "Tue Apr 19 15:38:02 2011 -0400"
      },
      "message": "rfkill: Regulator consumer driver for rfkill\n\nAdd a regulator consumer driver for rfkill to enable controlling radio\ntransmitters connected to voltage regulators using the regulator\nframework.\n\nA new \"vrfkill\" virtual supply is provided to use in platform code.\n\nSigned-off-by: Guiming Zhuo \u003cgmzhuo@gmail.com\u003e\nSigned-off-by: Antonio Ospite \u003cospite@studenti.unina.it\u003e\nReviewed-by: Johannes Berg \u003cjohannes@sipsolutions.net\u003e\nSigned-off-by: John W. Linville \u003clinville@tuxdriver.com\u003e\n"
    },
    {
      "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": "cf4328cd949c2086091c62c5685f1580fe9b55e4",
      "tree": "bd9d96f1c99910076b6f5f34cd5cd2da30405ef1",
      "parents": [
        "2396a22e0989df6038996506bfbf7a57f116c299"
      ],
      "author": {
        "name": "Ivo van Doorn",
        "email": "IvDoorn@gmail.com",
        "time": "Mon May 07 00:34:20 2007 -0700"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon May 07 00:34:20 2007 -0700"
      },
      "message": "[NET]: rfkill: add support for input key to control wireless radio\n\nThe RF kill patch that provides infrastructure for implementing\nswitches controlling radio states on various network and other cards.\n\n[dtor@insightbb.com: address review comments]\n[akpm@linux-foundation.org: cleanups, build fixes]\n\nSigned-off-by: Ivo van Doorn \u003cIvDoorn@gmail.com\u003e\nSigned-off-by: Andrew Morton \u003cakpm@linux-foundation.org\u003e\nSigned-off-by: Dmitry Torokhov \u003cdtor@mail.ru\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    }
  ]
}