)]}'
{
  "log": [
    {
      "commit": "4ef58d4e2ad1fa2a3e5bbf41af2284671fca8cf8",
      "tree": "856ba96302a36014736747e8464f80eeb827bbdd",
      "parents": [
        "f6c4c8195b5e7878823caa1181be404d9e86d369",
        "d014d043869cdc591f3a33243d3481fa4479c2d0"
      ],
      "author": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Wed Dec 09 19:43:33 2009 -0800"
      },
      "committer": {
        "name": "Linus Torvalds",
        "email": "torvalds@linux-foundation.org",
        "time": "Wed Dec 09 19:43:33 2009 -0800"
      },
      "message": "Merge branch \u0027for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial\n\n* \u0027for-linus\u0027 of git://git.kernel.org/pub/scm/linux/kernel/git/jikos/trivial: (42 commits)\n  tree-wide: fix misspelling of \"definition\" in comments\n  reiserfs: fix misspelling of \"journaled\"\n  doc: Fix a typo in slub.txt.\n  inotify: remove superfluous return code check\n  hdlc: spelling fix in find_pvc() comment\n  doc: fix regulator docs cut-and-pasteism\n  mtd: Fix comment in Kconfig\n  doc: Fix IRQ chip docs\n  tree-wide: fix assorted typos all over the place\n  drivers/ata/libata-sff.c: comment spelling fixes\n  fix typos/grammos in Documentation/edac.txt\n  sysctl: add missing comments\n  fs/debugfs/inode.c: fix comment typos\n  sgivwfb: Make use of ARRAY_SIZE.\n  sky2: fix sky2_link_down copy/paste comment error\n  tree-wide: fix typos \"couter\" -\u003e \"counter\"\n  tree-wide: fix typos \"offest\" -\u003e \"offset\"\n  fix kerneldoc for set_irq_msi()\n  spidev: fix double \"of of\" in comment\n  comment typo fix: sybsystem -\u003e subsystem\n  ...\n"
    },
    {
      "commit": "af901ca181d92aac3a7dc265144a9081a86d8f39",
      "tree": "380054af22521144fbe1364c3bcd55ad24c9bde4",
      "parents": [
        "972b94ffb90ea6d20c589d9a47215df103388ddd"
      ],
      "author": {
        "name": "André Goddard Rosa",
        "email": "andre.goddard@gmail.com",
        "time": "Sat Nov 14 13:09:05 2009 -0200"
      },
      "committer": {
        "name": "Jiri Kosina",
        "email": "jkosina@suse.cz",
        "time": "Fri Dec 04 15:39:55 2009 +0100"
      },
      "message": "tree-wide: fix assorted typos all over the place\n\nThat is \"success\", \"unknown\", \"through\", \"performance\", \"[re|un]mapping\"\n, \"access\", \"default\", \"reasonable\", \"[con]currently\", \"temperature\"\n, \"channel\", \"[un]used\", \"application\", \"example\",\"hierarchy\", \"therefore\"\n, \"[over|under]flow\", \"contiguous\", \"threshold\", \"enough\" and others.\n\nSigned-off-by: André Goddard Rosa \u003candre.goddard@gmail.com\u003e\nSigned-off-by: Jiri Kosina \u003cjkosina@suse.cz\u003e\n"
    },
    {
      "commit": "c2315b4ea9ac9c3f8caf03c3511d86fabe4a5fcd",
      "tree": "17e2d15abfd26fa83f8a9654bf581f6d40fc8c33",
      "parents": [
        "8f90f3ee83dc54e182d6a7548727cbae4b523e6e"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Wed Sep 16 17:10:55 2009 -0700"
      },
      "committer": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Mon Oct 19 15:56:07 2009 +0900"
      },
      "message": "wimax/i2400m: clarify and fix i2400m-\u003e{ready,updown}\n\nThe i2400m driver uses two different bits to distinguish how much the\ndriver is up. i2400m-\u003eready is used to denote that the infrastructure\nto communicate with the device is up and running. i2400m-\u003eupdown is\nused to indicate if \u0027ready\u0027 and the device is up and running, ready to\ntake control and data traffic.\n\nHowever, all this was pretty dirty and not clear, with many open spots\nwhere race conditions were present.\n\nThis commit cleans up the situation by:\n\n - documenting the usage of both bits\n\n - setting them only in specific, well controlled places\n   (i2400m_dev_start, i2400m_dev_stop)\n\n - ensuring the i2400m workqueue can\u0027t get in the middle of the\n   setting by flushing it when i2400m-\u003eready is set to zero. This\n   allows the report hook not having to check again for the bit to be\n   set [rx.c:i2400m_report_hook_work()].\n\n - using i2400m-\u003eupdown to determine if the device is up and running\n   instead of the wimax state in i2400m_dev_reset_handle().\n\n - not loosing missed messages sent by the hardware before\n   i2400m-\u003eready is set. In rx.c, whatever the device sends can be\n   sent to user space over the message pipes as soon as the wimax\n   device is registered, so don\u0027t wait for i2400m-\u003eready to be set.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.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": "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"
    }
  ]
}