)]}'
{
  "log": [
    {
      "commit": "3e91029ae049852c153da3fc355ab255ea7e2e0a",
      "tree": "4285f0df63d3099750999c57f4fef638e5177002",
      "parents": [
        "b0c83ae1de01880075955c7224e751440688ec74"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Sat Dec 20 16:57:42 2008 -0800"
      },
      "committer": {
        "name": "Greg Kroah-Hartman",
        "email": "gregkh@suse.de",
        "time": "Wed Jan 07 10:00:18 2009 -0800"
      },
      "message": "i2400m: documentation and instructions for usage\n\nThe driver for the i2400m is a stacked driver. There is a core driver,\nthe bus-generic driver that has no knowledge or dependencies on how\nthe device is connected to the system; it only knows how to speak the\ndevice protocol. Then there are the bus-specific drivers (for USB and\nSDIO) that provide backends for the generic driver to communicate with\nthe device.\n\nThe bus generic driver connects to the network and WiMAX stacks on the\ntop side, and on the bottom to the bus-specific drivers.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n"
    }
  ]
}
