From: Grant Likely <grant.likely@secretlab.ca>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, arm@kernel.org
Subject: Re: [GIT PULL] GPIO patch stack for v3.8
Date: Fri, 30 Nov 2012 11:17:48 +0000 [thread overview]
Message-ID: <20121130111748.B872E3E14C4@localhost> (raw)
In-Reply-To: <CACRpkdYDbfJO+RxbRpBmMi=mCj2L8a1rNgJgFW9EsxTPw2ivsA@mail.gmail.com>
On Thu, 22 Nov 2012 10:30:27 +0100, Linus Walleij <linus.walleij@linaro.org> wrote:
> Hi Grant,
>
> to avoid any mess during the v3.8 merge window, could you please pull
> this patch stack to your GPIO branch for v3.8?
>
> All these patches have been resting in linux-next and are reviewed and
> ACKed by maintainers. A more verbose description is in the signed
> tag.
>
> Some confusion stems from the fact that I applied my own patches
> without replying to myself that I applied them ... split personality/role
> problem. If you pull this in, things should be more clear on what's
> queued and not - everything is in your tree.
>
> Note that ARM SoC is already using parts of this tree as baseline
> for stuff in their tree so rebasing this patch trail is *not*
> recommended.
Don't worry, I won't rebase anything that I grab out of your tree.
> Please pull it in!
>
> Apart from this there are a few gpiolib patches in the pinctrl tree as
> well. Those are about adding the GPIOchip local GPIO numberspace
> to pinctrl local numberspace ranges as we discussed with Dong
> Aisheng in Hong Kong, I'd be happy to brief you on the implementation
> if need be. It's also detailed here:
> https://blueprints.launchpad.net/linux-linaro/+spec/pinctrl-gpiorange-makeover
Those are fine.
g.
prev parent reply other threads:[~2012-11-30 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 9:30 [GIT PULL] GPIO patch stack for v3.8 Linus Walleij
2012-11-30 11:17 ` Grant Likely [this message]
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=20121130111748.B872E3E14C4@localhost \
--to=grant.likely@secretlab.ca \
--cc=arm@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).