)]}'
{
  "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": "816af3bb5022c1468b3d826c645ddc2cac45bc97",
      "tree": "1b2a6abc75c00366f71c820ae946f4bdce4d90d9",
      "parents": [
        "1ea6b8f48918282bdca0b32a34095504ee65bab5"
      ],
      "author": {
        "name": "Axel Lin",
        "email": "axel.lin@gmail.com",
        "time": "Thu Nov 03 14:45:48 2011 +0800"
      },
      "committer": {
        "name": "Ohad Ben-Cohen",
        "email": "ohad@wizery.com",
        "time": "Tue Nov 08 09:28:27 2011 +0200"
      },
      "message": "hwspinlock: Don\u0027t return a value in __hwspin_unlock\n\nFix below build warning:\n\n  CC      arch/arm/mach-omap2/hwspinlock.o\nIn file included from arch/arm/mach-omap2/hwspinlock.c:22:\ninclude/linux/hwspinlock.h: In function \u0027__hwspin_unlock\u0027:\ninclude/linux/hwspinlock.h:121: warning: \u0027return\u0027 with a value, in function returning void\n\nSigned-off-by: Axel Lin \u003caxel.lin@gmail.com\u003e\nSigned-off-by: Ohad Ben-Cohen \u003cohad@wizery.com\u003e\n"
    },
    {
      "commit": "300bab9770e2bd10262bcc78e7249fdce2c74b38",
      "tree": "5c23d7dce82b96fa177ea7c854de7f4b36992c80",
      "parents": [
        "c536abfdf5227987b8a72ff955b64e62fd58fe91"
      ],
      "author": {
        "name": "Ohad Ben-Cohen",
        "email": "ohad@wizery.com",
        "time": "Tue Sep 06 15:39:21 2011 +0300"
      },
      "committer": {
        "name": "Ohad Ben-Cohen",
        "email": "ohad@wizery.com",
        "time": "Wed Sep 21 19:45:34 2011 +0300"
      },
      "message": "hwspinlock/core: register a bank of hwspinlocks in a single API call\n\nHardware Spinlock devices usually contain numerous locks (known\ndevices today support between 32 to 256 locks).\n\nOriginally hwspinlock core required drivers to register (and later,\nwhen needed, unregister) each lock separately.\n\nThat worked, but required hwspinlocks drivers to do a bit extra work\nwhen they were probed/removed.\n\nThis patch changes hwspin_lock_{un}register() to allow a bank of\nhwspinlocks to be {un}registered in a single invocation.\n\nA new \u0027struct hwspinlock_device\u0027, which contains an array of \u0027struct\nhwspinlock\u0027s is now being passed to the core upon registration (so\ninstead of wrapping each struct hwspinlock, a priv member has been added\nto allow drivers to piggyback their private data with each hwspinlock).\n\nWhile at it, several per-lock members were moved to be per-device:\n1. struct device *dev\n2. struct hwspinlock_ops *ops\n\nIn addition, now that the array of locks is handled by the core,\nthere\u0027s no reason to maintain a per-lock \u0027int id\u0027 member: the id of the\nlock anyway equals to its index in the bank\u0027s array plus the bank\u0027s\nbase_id.\nRemove this per-lock id member too, and instead use a simple pointers\narithmetic to derive it.\n\nAs a result of this change, hwspinlocks drivers are now simpler and smaller\n(about %20 code reduction) and the memory footprint of the hwspinlock\nframework is reduced.\n\nSigned-off-by: Ohad Ben-Cohen \u003cohad@wizery.com\u003e\n"
    },
    {
      "commit": "c536abfdf5227987b8a72ff955b64e62fd58fe91",
      "tree": "7ba44299990776920e0b765916311009a6bf1e1f",
      "parents": [
        "93b465c2e186d96fb90012ba0f9372eb9952e732"
      ],
      "author": {
        "name": "Ohad Ben-Cohen",
        "email": "ohad@wizery.com",
        "time": "Thu Sep 08 21:16:17 2011 +0300"
      },
      "committer": {
        "name": "Ohad Ben-Cohen",
        "email": "ohad@wizery.com",
        "time": "Wed Sep 21 19:45:34 2011 +0300"
      },
      "message": "hwspinlock/core: remove stubs for register/unregister\n\nhwspinlock drivers must anyway select CONFIG_HWSPINLOCK,\nso there\u0027s no point in having register/unregister stubs.\n\nRemoving those stubs will only make it easier for developers\nto catch CONFIG_HWSPINLOCK mis-.config-urations.\n\nSigned-off-by: Ohad Ben-Cohen \u003cohad@wizery.com\u003e\n"
    },
    {
      "commit": "c3c1250e93a7ab1327a9fc49d2a22405672f4204",
      "tree": "2dc99df2ab4657de87a66da7d0a047a95ff27711",
      "parents": [
        "c97f6dd0fe21dfd658c59c144a1b7fd5d8db04ac"
      ],
      "author": {
        "name": "Ohad Ben-Cohen",
        "email": "ohad@wizery.com",
        "time": "Mon Sep 05 23:15:06 2011 +0300"
      },
      "committer": {
        "name": "Ohad Ben-Cohen",
        "email": "ohad@wizery.com",
        "time": "Wed Sep 21 19:45:32 2011 +0300"
      },
      "message": "hwspinlock/core/omap: fix id issues on multiple hwspinlock devices\n\nhwspinlock devices provide system-wide hardware locks that are used\nby remote processors that have no other way to achieve synchronization.\n\nTo achieve that, each physical lock must have a system-wide id number\nthat is agreed upon, otherwise remote processors can\u0027t possibly assume\nthey\u0027re using the same hardware lock.\n\nUsually boards have a single hwspinlock device, which provides several\nhwspinlocks, and in this case, they can be trivially numbered 0 to\n(num-of-locks - 1).\n\nIn case boards have several hwspinlocks devices, a different base id\nshould be used for each hwspinlock device (they can\u0027t all use 0 as\na starting id!).\n\nWhile this is certainly not common, it\u0027s just plain wrong to just\nsilently use 0 as a base id whenever the hwspinlock driver is probed.\n\nThis patch provides a hwspinlock_pdata structure, that boards can use\nto set a different base id for each of the hwspinlock devices they may\nhave, and demonstrates how to use it with the omap hwspinlock driver.\n\nWhile we\u0027re at it, make sure the hwspinlock core prints an explicit\nerror message in case an hwspinlock is registered with an id number\nthat already exists; this will help users catch such base id issues.\n\nReported-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nSigned-off-by: Ohad Ben-Cohen \u003cohad@wizery.com\u003e\nAcked-by: Tony Lindgren \u003ctony@atomide.com\u003e\n"
    },
    {
      "commit": "bd9a4c7df256cee4e9f6a4b56baa3b89d63f0f1e",
      "tree": "ee6ca0aaebd8e553576a0cf3fefafa1cd3ec8e1d",
      "parents": [
        "d9e45731debd83e2b249be349993595907dddeae"
      ],
      "author": {
        "name": "Ohad Ben-Cohen",
        "email": "ohad@wizery.com",
        "time": "Thu Feb 17 09:52:03 2011 -0800"
      },
      "committer": {
        "name": "Tony Lindgren",
        "email": "tony@atomide.com",
        "time": "Thu Feb 17 09:52:03 2011 -0800"
      },
      "message": "drivers: hwspinlock: add framework\n\nAdd a platform-independent hwspinlock framework.\n\nHardware spinlock devices are needed, e.g., in order to access data\nthat is shared between remote processors, that otherwise have no\nalternative mechanism to accomplish synchronization and mutual exclusion\noperations.\n\nSigned-off-by: Ohad Ben-Cohen \u003cohad@wizery.com\u003e\nCc: Hari Kanigeri \u003ch-kanigeri2@ti.com\u003e\nCc: Benoit Cousson \u003cb-cousson@ti.com\u003e\nCc: Kevin Hilman \u003ckhilman@ti.com\u003e\nCc: Grant Likely \u003cgrant.likely@secretlab.ca\u003e\nCc: Paul Walmsley \u003cpaul@pwsan.com\u003e\nCc: Russell King \u003clinux@arm.linux.org.uk\u003e\nAcked-by: Arnd Bergmann \u003carnd@arndb.de\u003e\nSigned-off-by: Tony Lindgren \u003ctony@atomide.com\u003e\n"
    }
  ]
}