Re: [GIT PULL] gpio changes for v3.9; second round

[Grant Likely]

On Mon, Mar 4, 2013 at 5:32 AM, Grant Likely <grant.likely@xxxxxxxxxxxx> wrote:
> On Mon, Mar 4, 2013 at 2:50 AM, Linus Torvalds
> <torvalds@xxxxxxxxxxxxxxxxxxxx> wrote:
>> Should this driver depend on CONFIG_OF_GPIO, or should it have
>> #ifdef's? Regardless, it's clearly broken right now.
>>
>> Unpulled.
>
> Ugh. Well I clearly screwed that up. Sorry. I'll fix that right away.

Okay, I've dropped the top two commits from that tag. The broken
commit and the one above it were certainly not critical. They can wait
until v3.10. Here's a new pull request.

g.

The following changes since commit b0af9cd9aab60ceb17d3ebabb9fdf4ff0a99cf50:

  Merge tag 'lzo-update-signature-20130226' of
git://github.com/markus-oberhumer/linux (2013-02-28 20:45:52 -0800)

are available in the git repository at:


  git://git.secretlab.ca/git/linux tags/gpio-for-linus

for you to fetch changes up to e97f9b5277afeabb54892ebc6f68500098467ba1:

  gpio/gpio-ich: fix ichx_gpio_check_available() return what callers
expect (2013-03-02 13:20:21 +0000)

----------------------------------------------------------------
2nd round of GPIO changes for Linux 3.9

This branch contains a few bug fixes that I missed the first time around
and updates to the gpio_desc series included in the first pull request.
This tag has been retagged to drop the 2 head commits because the one of
them caused a build failure.

----------------------------------------------------------------
Alexandre Courbot (3):
      gpiolib: check descriptors validity before use
      gpiolib: use const parameters when possible
      gpiolib: move comment to right function

Mika Westerberg (1):
      gpio/gpio-ich: fix ichx_gpio_check_available() return what callers expect

 drivers/gpio/gpio-ich.c |    4 +-
 drivers/gpio/gpiolib.c  |  143 +++++++++++++++++++++++++++--------------------
 2 files changed, 84 insertions(+), 63 deletions(-)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/