From: linus.walleij@linaro.org (Linus Walleij)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 12/12] ARM: ux500: switch MSP to using pinctrl for pins
Date: Fri, 11 May 2012 10:33:08 +0200 [thread overview]
Message-ID: <CACRpkdYRv5w=P4zTLZiG69rMN5Rt-yah4EdgWfg03oD7Tcvzqw@mail.gmail.com> (raw)
In-Reply-To: <4FAAD95D.9010108@wwwdotorg.org>
On Wed, May 9, 2012 at 10:53 PM, Stephen Warren <swarren@wwwdotorg.org> wrote:
> On 05/08/2012 03:45 AM, Linus Walleij wrote:
>> From: Linus Walleij <linus.walleij@linaro.org>
>>
>> The MSP platform data callbacks use the old custom callbacks to
>> set the state of the pins, switch over to using pinctrl.
>
> Aside from the comments I've already made, I guess you can consider the
> whole series:
>
> Acked-by: Stephen Warren <swarren@wwwdotorg.org>
Thanks Stephen! Pushing this through ARM SoC.
Yours,
Linus Walleij
prev parent reply other threads:[~2012-05-11 8:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 9:45 [PATCH 12/12] ARM: ux500: switch MSP to using pinctrl for pins Linus Walleij
2012-05-09 20:53 ` Stephen Warren
2012-05-11 8:33 ` Linus Walleij [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='CACRpkdYRv5w=P4zTLZiG69rMN5Rt-yah4EdgWfg03oD7Tcvzqw@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--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 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).