All of lore.kernel.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] SPEAr pinctrl updates for v-3.5
Date: Sat, 12 May 2012 21:42:01 +0000	[thread overview]
Message-ID: <201205122142.02318.arnd@arndb.de> (raw)
In-Reply-To: <CAOh2x=mGdV_wbJC64wvb9+UV_FBgnsat9=ojD8BJYVxT+HoWhQ@mail.gmail.com>

On Thursday 10 May 2012, viresh kumar wrote:
> The following changes since commit 9f05a80564c35c397c5ce0f0b1106a420c3f5bdc:
> 
>   SPEAr: Update defconfigs (2012-05-10 16:15:08 +0530)
> 
> are available in the git repository at:
> 
>   git://git.stlinux.com/spear/linux-2.6.git for-v3.5-spear-pinctrl-update
> 
> for you to fetch changes up to 560a7694d63e2461912d3b99987a3c89ea4b56e2:
> 
>   SPEAr: Add plgpio node in device tree dtsi files (2012-05-10 16:15:09 +0530)
> 
> ----------------------------------------------------------------
> Viresh Kumar (6):
>       gpiolib: Add of_get_gpio_chip_by_phandle() helper
>       pinctrl: SPEAr: Don't set all non muxreg bits on pinctrl_disable
>       pinctrl: SPEAr1310: Fix pin numbers for clcd_high_res
>       pinctrl: SPEAr: Add plgpio driver
>       pinctrl: SPEAr: Add gpio ranges support
>       SPEAr: Add plgpio node in device tree dtsi files

Hi Viresh,

I thought the first patch "gpiolib: Add of_get_gpio_chip_by_phandle() helper"
was not actually accepted. What was the outcome of that discussion?

	Arnd

  reply	other threads:[~2012-05-12 21:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-09 11:15 [GIT PULL] SPEAr pinctrl updates for v-3.5 Viresh Kumar
2012-05-10 11:33 ` viresh kumar
2012-05-12 21:42   ` Arnd Bergmann [this message]
2012-05-12 23:54     ` Linus Walleij
2012-05-14  4:02       ` Viresh Kumar
2012-05-17  4:26       ` Viresh Kumar
2012-05-20 20:45         ` Linus Walleij
2012-06-19 14:11           ` viresh kumar
2012-06-20  8:25             ` Linus Walleij
2012-09-01 11:22               ` shiraz hashim
2012-09-03 11:48                 ` Linus Walleij
2012-09-04  4:19                   ` Shiraz Hashim
2012-09-04  7:17                     ` Linus Walleij
2012-10-27  9:33                   ` viresh kumar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=201205122142.02318.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.