)]}'
{
  "log": [
    {
      "commit": "313162d0b83836e2f57e51b9b8650fb4b9c396ea",
      "tree": "8f39f20515a924d392cf9a72db0918fda07a34c7",
      "parents": [
        "51990e825431089747f8896244b5c17d3a6423f1"
      ],
      "author": {
        "name": "Paul Gortmaker",
        "email": "paul.gortmaker@windriver.com",
        "time": "Mon Jan 30 11:46:54 2012 -0500"
      },
      "committer": {
        "name": "Paul Gortmaker",
        "email": "paul.gortmaker@windriver.com",
        "time": "Fri Mar 16 10:38:24 2012 -0400"
      },
      "message": "device.h: audit and cleanup users in main include dir\n\nThe \u003clinux/device.h\u003e header includes a lot of stuff, and\nit in turn gets a lot of use just for the basic \"struct device\"\nwhich appears so often.\n\nClean up the users as follows:\n\n1) For those headers only needing \"struct device\" as a pointer\nin fcn args, replace the include with exactly that.\n\n2) For headers not really using anything from device.h, simply\ndelete the include altogether.\n\n3) For headers relying on getting device.h implicitly before\nbeing included themselves, now explicitly include device.h\n\n4) For files in which doing #1 or #2 uncovers an implicit\ndependency on some other header, fix by explicitly adding\nthe required header(s).\n\nAny C files that were implicitly relying on device.h to be\npresent have already been dealt with in advance.\n\nTotal removals from #1 and #2: 51.  Total additions coming\nfrom #3: 9.  Total other implicit dependencies from #4: 7.\n\nAs of 3.3-rc1, there were 110, so a net removal of 42 gives\nabout a 38% reduction in device.h presence in include/*\n\nSigned-off-by: Paul Gortmaker \u003cpaul.gortmaker@windriver.com\u003e\n"
    },
    {
      "commit": "5a0e3ad6af8660be21ca98a971cd00f331318c05",
      "tree": "5bfb7be11a03176a87296a43ac6647975c00a1d1",
      "parents": [
        "ed391f4ebf8f701d3566423ce8f17e614cde9806"
      ],
      "author": {
        "name": "Tejun Heo",
        "email": "tj@kernel.org",
        "time": "Wed Mar 24 17:04:11 2010 +0900"
      },
      "committer": {
        "name": "Tejun Heo",
        "email": "tj@kernel.org",
        "time": "Tue Mar 30 22:02:32 2010 +0900"
      },
      "message": "include cleanup: Update gfp.h and slab.h includes to prepare for breaking implicit slab.h inclusion from percpu.h\n\npercpu.h is included by sched.h and module.h and thus ends up being\nincluded when building most .c files.  percpu.h includes slab.h which\nin turn includes gfp.h making everything defined by the two files\nuniversally available and complicating inclusion dependencies.\n\npercpu.h -\u003e slab.h dependency is about to be removed.  Prepare for\nthis change by updating users of gfp and slab facilities include those\nheaders directly instead of assuming availability.  As this conversion\nneeds to touch large number of source files, the following script is\nused as the basis of conversion.\n\n  http://userweb.kernel.org/~tj/misc/slabh-sweep.py\n\nThe script does the followings.\n\n* Scan files for gfp and slab usages and update includes such that\n  only the necessary includes are there.  ie. if only gfp is used,\n  gfp.h, if slab is used, slab.h.\n\n* When the script inserts a new include, it looks at the include\n  blocks and try to put the new include such that its order conforms\n  to its surrounding.  It\u0027s put in the include block which contains\n  core kernel includes, in the same order that the rest are ordered -\n  alphabetical, Christmas tree, rev-Xmas-tree or at the end if there\n  doesn\u0027t seem to be any matching order.\n\n* If the script can\u0027t find a place to put a new include (mostly\n  because the file doesn\u0027t have fitting include block), it prints out\n  an error message indicating which .h file needs to be added to the\n  file.\n\nThe conversion was done in the following steps.\n\n1. The initial automatic conversion of all .c files updated slightly\n   over 4000 files, deleting around 700 includes and adding ~480 gfp.h\n   and ~3000 slab.h inclusions.  The script emitted errors for ~400\n   files.\n\n2. Each error was manually checked.  Some didn\u0027t need the inclusion,\n   some needed manual addition while adding it to implementation .h or\n   embedding .c file was more appropriate for others.  This step added\n   inclusions to around 150 files.\n\n3. The script was run again and the output was compared to the edits\n   from #2 to make sure no file was left behind.\n\n4. Several build tests were done and a couple of problems were fixed.\n   e.g. lib/decompress_*.c used malloc/free() wrappers around slab\n   APIs requiring slab.h to be added manually.\n\n5. The script was run on all .h files but without automatically\n   editing them as sprinkling gfp.h and slab.h inclusions around .h\n   files could easily lead to inclusion dependency hell.  Most gfp.h\n   inclusion directives were ignored as stuff from gfp.h was usually\n   wildly available and often used in preprocessor macros.  Each\n   slab.h inclusion directive was examined and added manually as\n   necessary.\n\n6. percpu.h was updated not to include slab.h.\n\n7. Build test were done on the following configurations and failures\n   were fixed.  CONFIG_GCOV_KERNEL was turned off for all tests (as my\n   distributed build env didn\u0027t work with gcov compiles) and a few\n   more options had to be turned off depending on archs to make things\n   build (like ipr on powerpc/64 which failed due to missing writeq).\n\n   * x86 and x86_64 UP and SMP allmodconfig and a custom test config.\n   * powerpc and powerpc64 SMP allmodconfig\n   * sparc and sparc64 SMP allmodconfig\n   * ia64 SMP allmodconfig\n   * s390 SMP allmodconfig\n   * alpha SMP allmodconfig\n   * um on x86_64 SMP allmodconfig\n\n8. percpu.h modifications were reverted so that it could be applied as\n   a separate patch and serve as bisection point.\n\nGiven the fact that I had only a couple of failures from tests on step\n6, I\u0027m fairly confident about the coverage of this conversion patch.\nIf there is a breakage, it\u0027s likely to be something in one of the arch\nheaders which should be easily discoverable easily on most builds of\nthe specific arch.\n\nSigned-off-by: Tejun Heo \u003ctj@kernel.org\u003e\nGuess-its-ok-by: Christoph Lameter \u003ccl@linux-foundation.org\u003e\nCc: Ingo Molnar \u003cmingo@redhat.com\u003e\nCc: Lee Schermerhorn \u003cLee.Schermerhorn@hp.com\u003e\n"
    },
    {
      "commit": "7329012e673231dee9a21567cfb9881f5ea462ba",
      "tree": "676f665bf8ca7f52923ed388db109ad2807c305c",
      "parents": [
        "f8fc3295570115267ce1ce901f362d13d194aefc"
      ],
      "author": {
        "name": "Dirk Brandewie",
        "email": "dirk.j.brandewie@intel.com",
        "time": "Wed Aug 12 11:29:46 2009 -0700"
      },
      "committer": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Mon Oct 19 15:55:59 2009 +0900"
      },
      "message": "wimax/i6x50: add Intel WiFi/WiMAX Link 6050 Series support\n\nAdd support for the WiMAX device in the Intel WiFi/WiMAX Link 6050\nSeries; this involves:\n\n - adding the device ID to bind to and an endpoint mapping for the\n   driver to use.\n\n - at probe() time, some things are set depending on the device id:\n\n   + the list of firmware names to try\n\n   + mapping of endpoints\n\nSigned-off-by: Dirk Brandewie \u003cdirk.j.brandewie@intel.com\u003e\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\n"
    },
    {
      "commit": "923d708fed9d47c7b4d67694500d766337663e29",
      "tree": "54cc91baf9f495f924e467625e2bf50cbce79f48",
      "parents": [
        "ebc5f62b76ad540ff7b3e438506638009e7812a6"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Fri Sep 04 14:50:59 2009 -0700"
      },
      "committer": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Mon Oct 19 15:55:55 2009 +0900"
      },
      "message": "wimax/i2400m: fix reboot echo/ack barker deadlock\n\nThe i2400m based devices can get in a sort of a deadlock some times;\nwhen they boot, they send a reboot \"barker\" (a magic number) and then\nthe driver has to echo that same barker to ack reception\n(echo/ack). Then the device does a final ack by sending an ACK barker.\n\nThe first time this happens, we don\u0027t know ahead of time with barker\nthe device is going to send, as different device models and SKUs will\nsend different barker depending on the EEPROM programming.\n\nIf the device has sent the barker before the driver has been able to\nread it, the driver looses, as it doesn\u0027t know which barker it has to\necho/ack back. With older devices, we tried a couple of combinations\nand that always worked; but now, with adding support for more, in\nwhich we have an unlimited number of new barkers, that is not an\noption.\n\nSo we rework said case so that when the device gets stuck, we just\ncycle through all the known types until one forces the device to send\nan ack. Otherwise, the driver gives up and aborts.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\n"
    },
    {
      "commit": "32742e6158657f19ad31653705bef56d983508e7",
      "tree": "05a13b990dac551c18e1fd468ca1383b86f40e0c",
      "parents": [
        "59bdc4be0b819173a8f840fc11ccb82d6f2ca64b"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Thu Sep 03 15:56:40 2009 -0700"
      },
      "committer": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Mon Oct 19 15:55:52 2009 +0900"
      },
      "message": "wimax/i2400m: decide properly if using signed vs non-signed firmware loading\n\nThe i2400m based devices can boot two main types of firmware images:\nsigned and non-signed. Signed images have signature data included that\nmust match that of a certificate stored in the device.\n\nCurrently the code is making the decission on what type of firmware\nload (signed vs non-signed) is going to be loaded based on a hardcoded\ndecission in __i2400m_ack_verify(), based on the barker the device\nsent upon boot.\n\nThis is not flexible enough as future hardware will emit more barkers;\nthus the bit has to be set in a place where there is better knowledge\nof what is going on. This will be done in follow-up commits -- however\nthis patch paves the way for it.\n\nSo the querying of the mode is packed into i2400m_boot_is_signed();\nthe main changes are just using i2400m_boot_is_signed() to determine\nthe method to follow and setting i2400m-\u003esboot in\ni2400m_is_boot_barker(). The modifications in i2400m_dnload_init() and\ni2400m_dnload_finalize() are just reorganizing the order of the if\nblocks and thus look larger than they really are.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\n"
    },
    {
      "commit": "4c2b1a11646bf74e2926ce8b13a21884adc1e05c",
      "tree": "59cd5b59b21969264c6833b567b828484a6d76ed",
      "parents": [
        "4dc1bf074e4db5aa281a7b82ceebb24df98922d2"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Wed Sep 02 15:36:05 2009 -0700"
      },
      "committer": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Mon Oct 19 15:55:50 2009 +0900"
      },
      "message": "wimax: allow specifying debug levels as command line option\n\nAdd \"debug\" module options to all the wimax modules (including\ndrivers) so that the debug levels can be set upon kernel boot or\nmodule load time.\n\nThis is needed as currently there was a limitation where the debug\nlevels could only be set when a device was succesfully\nenumerated. This made it difficult to debug issues that made a device\nnot probe properly.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\n"
    },
    {
      "commit": "8593a1967fb9746d318dde88a0a39a36dbfc3445",
      "tree": "6e3d5e259ae08eab71c8442b2f7fa66bd1d39867",
      "parents": [
        "10b1de6b774a531c9054ee01e734a85ffbab179e"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Wed May 20 16:53:30 2009 -0700"
      },
      "committer": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Thu Jun 11 03:30:20 2009 -0700"
      },
      "message": "wimax/i2400m: rename misleading I2400M_PL_PAD to I2400M_PL_ALIGN\n\nThe constant is being use as an alignment factor, not as a padding\nfactor; made reading/reviewing the code quite confusing.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\n"
    },
    {
      "commit": "c747583d19d5d5147a9f0eae480c1fdbc84c4252",
      "tree": "e0af269356987f4096eb44b659bb874431264294",
      "parents": [
        "61b8d2688a0cc9434b18144342c719f809691d72"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Sat Feb 28 23:42:54 2009 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon Mar 02 03:10:28 2009 -0800"
      },
      "message": "wimax/i2400m: implement RX reorder support\n\nAllow the device to give the driver RX data with reorder information.\n\nWhen that is done, the device will indicate the driver if a packet has\nto be held in a (sorted) queue. It will also tell the driver when held\npackets have to be released to the OS.\n\nThis is done to improve the WiMAX-protocol level retransmission\nsupport when missing frames are detected.\n\nThe code docs provide details about the implementation.\n\nIn general, this just hooks into the RX path in rx.c; if a packet with\nthe reorder bit in the RX header is detected, the reorder information\nin the header is extracted and one of the four main reorder operations\nare executed. In one case (queue) no packet will be delivered to the\nnetworking stack, just queued, whereas in the others (reset, update_ws\nand queue_update_ws), queued packet might be delivered depending on\nthe window start for the specific queue.\n\nThe modifications to files other than rx.c are:\n\n- control.c: during device initialization, enable reordering support\n  if the rx_reorder_disabled module parameter is not enabled\n\n- driver.c: expose a rx_reorder_disable module parameter and call\n  i2400m_rx_setup/release() to initialize/shutdown RX reorder\n  support.\n\n- i2400m.h: introduce members in \u0027struct i2400m\u0027 needed for\n  implementing reorder support.\n\n- linux/i2400m.h: introduce TLVs, commands and constant definitions\n  related to RX reorder\n\nLast but not least, the rx reorder code includes an small circular log\nwhere the last N reorder operations are recorded to be displayed in\ncase of inconsistency. Otherwise diagnosing issues would be almost\nimpossible.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "fd5c565c0c04d2716cfdac3f1de3c2261d6a457d",
      "tree": "0f64176368c6ffb5b4f95abf37b422bfba7fdd6e",
      "parents": [
        "347707baa77d273d79258303e00200d40cf3b323"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Sat Feb 28 23:42:52 2009 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon Mar 02 03:10:26 2009 -0800"
      },
      "message": "wimax/i2400m: support extended data RX protocol (no need to reallocate skbs)\n\nNewer i2400m firmwares (\u003e\u003d v1.4) extend the data RX protocol so that\neach packet has a 16 byte header. This header is mainly used to\nimplement host reordeing (which is addressed in later commits).\n\nHowever, this header also allows us to overwrite it (once data has\nbeen extracted) with an Ethernet header and deliver to the networking\nstack without having to reallocate the skb (as it happened in fw \u003c\u003d\nv1.3) to make room for it.\n\n- control.c: indicate the device [dev_initialize()] that the driver\n  wants to use the extended data RX protocol. Also involves adding the\n  definition of the needed data types in include/linux/wimax/i2400m.h.\n\n- rx.c: handle the new payload type for the extended RX data\n  protocol. Prepares the skb for delivery to\n  netdev.c:i2400m_net_erx().\n\n- netdev.c: Introduce i2400m_net_erx() that adds the fake ethernet\n  address to a prepared skb and delivers it to the networking\n  stack.\n\n- cleanup: in most instances in rx.c, the variable \u0027single\u0027 was\n  renamed to \u0027single_last\u0027 for it better conveys its meaning.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "347707baa77d273d79258303e00200d40cf3b323",
      "tree": "fb0ebb6f2f7b063948aa30ba836d1fe3a9405512",
      "parents": [
        "8987691a4aa6622a1b58bb12c56abaf3d2098fad"
      ],
      "author": {
        "name": "Kay Sievers",
        "email": "kay.sievers@vrfy.org",
        "time": "Sat Feb 28 23:42:51 2009 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon Mar 02 03:10:26 2009 -0800"
      },
      "message": "wimax: struct device - replace bus_id with dev_name(), dev_set_name()\n\nCc: inaky.perez-gonzalez@intel.com\nCc: linux-wimax@intel.com\nAcked-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\nSigned-off-by: Kay Sievers \u003ckay.sievers@vrfy.org\u003e\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "8987691a4aa6622a1b58bb12c56abaf3d2098fad",
      "tree": "92da0abdf6a29aa60ec5aff6250b1937d4c264d6",
      "parents": [
        "6a0f7ab8305cb60a43a6c4a548f57adab784e6cd"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Sat Feb 28 23:42:50 2009 +0000"
      },
      "committer": {
        "name": "David S. Miller",
        "email": "davem@davemloft.net",
        "time": "Mon Mar 02 03:10:25 2009 -0800"
      },
      "message": "wimax/i2400m: allow control of the base-station idle mode timeout\n\nFor power saving reasons, WiMAX links can be put in idle mode while\nconnected after a certain time of the link not being used for tx or\nrx. In this mode, the device pages the base-station regularly and when\ndata is ready to be transmitted, the link is revived.\n\nThis patch allows the user to control the time the device has to be\nidle before it decides to go to idle mode from a sysfs\ninterace.\n\nIt also updates the initialization code to acknowledge the module\nvariable \u0027idle_mode_disabled\u0027 when the firmware is a newer version\n(upcoming 1.4 vs 2.6.29\u0027s v1.3).\n\nThe method for setting the idle mode timeout in the older firmwares is\nmuch more limited and can be only done at initialization time. Thus,\nthe sysfs file will return -ENOSYS on older ones.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: David S. Miller \u003cdavem@davemloft.net\u003e\n"
    },
    {
      "commit": "e30698743419d20dce03d033761f203b4d847ab0",
      "tree": "95c5844eedd59a419dae38b52c7bbbf88ea0bcaa",
      "parents": [
        "143ee2d5557c0598a97f3089eb29e8226e0e8cee"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Sat Dec 20 16:57:59 2008 -0800"
      },
      "committer": {
        "name": "Greg Kroah-Hartman",
        "email": "gregkh@suse.de",
        "time": "Wed Jan 07 10:00:22 2009 -0800"
      },
      "message": "wimax: export linux/wimax.h and linux/wimax/i2400m.h with headers_install\n\nThese two files are what user space can use to establish communication\nwith the WiMAX kernel API and to speak the Intel 2400m Wireless WiMAX\nconnection\u0027s control protocol.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nCc: David Woodhouse \u003cdwmw2@infradead.org\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n"
    },
    {
      "commit": "ea24652d253eabfb83e955e55ce032228d9d99b9",
      "tree": "9cad05e40ec16a35231afad3cb3c9d5c40f05c36",
      "parents": [
        "3e91029ae049852c153da3fc355ab255ea7e2e0a"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Sat Dec 20 16:57:43 2008 -0800"
      },
      "committer": {
        "name": "Greg Kroah-Hartman",
        "email": "gregkh@suse.de",
        "time": "Wed Jan 07 10:00:18 2009 -0800"
      },
      "message": "i2400m: host/device procotol and core driver definitions\n\nThe wimax/i2400m.h defines the structures and constants for the\nhost-device protocols:\n\n - boot / firmware upload protocol\n\n - general data transport protocol\n\n - control protocol\n\nIt is done in such a way that can also be used verbatim by user space.\n\ndrivers/net/wimax/i2400m.h defines all the APIs used by the core,\nbus-generic driver (i2400m) and the bus specific drivers\n(i2400m-BUSNAME). It also gives a roadmap to the driver\nimplementation.\n\ndebug-levels.h adds the core driver\u0027s debug settings.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n"
    },
    {
      "commit": "ea912f4e7f264981faf8665cfb63d46d7f948117",
      "tree": "b0bfe3d7abcee4beb935f0391b8c0180ccb56941",
      "parents": [
        "60fa9ca6cfff2be4132ea93b7dd632801ec0c817"
      ],
      "author": {
        "name": "Inaky Perez-Gonzalez",
        "email": "inaky@linux.intel.com",
        "time": "Sat Dec 20 16:57:35 2008 -0800"
      },
      "committer": {
        "name": "Greg Kroah-Hartman",
        "email": "gregkh@suse.de",
        "time": "Wed Jan 07 10:00:17 2009 -0800"
      },
      "message": "wimax: debug macros and debug settings for the WiMAX stack\n\nThis file contains a simple debug framework that is used in the stack;\nit allows the debug level to be controlled at compile-time (so the\ndebug code is optimized out) and at run-time (for what wasn\u0027t compiled\nout).\n\nThis is eventually going to be moved to use dynamic_printk(). Just\nneed to find time to do it.\n\nSigned-off-by: Inaky Perez-Gonzalez \u003cinaky@linux.intel.com\u003e\nSigned-off-by: Greg Kroah-Hartman \u003cgregkh@suse.de\u003e\n\n"
    }
  ]
}