From: Dong Aisheng <aisheng.dong@freescale.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Guo Shawn-R65073 <r65073@freescale.com>,
Dong Aisheng-B29396 <B29396@freescale.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH 1/2] pinctrl: pinctrl-imx: add imx53 pinctrl driver
Date: Wed, 16 May 2012 15:57:55 +0800 [thread overview]
Message-ID: <20120516075754.GG10347@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <CACRpkdZw5Sag5dmpqadTPJyaT5hex1CnASeVRKT5FXWtOKijkQ@mail.gmail.com>
On Wed, May 16, 2012 at 02:50:48PM +0800, Linus Walleij wrote:
> On Wed, May 16, 2012 at 4:13 AM, Shawn Guo <shawn.guo@freescale.com> wrote:
>
> > With the patches going in via pinctrl tree, we can start making machine
> > changes from next cycle.
>
> Shawn are these patches OK with you? It'd be nice to have some
> Acked-by: since they are quite big.
>
Shawn said he's ok with it, but he's not available right now.
Maybe you could hold a few hours to wait for his tag if needed.
Regards
Dong Aisheng
next prev parent reply other threads:[~2012-05-16 7:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-14 15:46 Dong Aisheng
2012-05-14 15:46 ` [PATCH 2/2] pinctrl: pinctrl-imx: add imx51 " Dong Aisheng
2012-05-15 6:44 ` [PATCH 1/2] pinctrl: pinctrl-imx: add imx53 " Dong Aisheng
2012-05-15 11:10 ` Linus Walleij
2012-05-15 11:27 ` Dong Aisheng
2012-05-15 12:33 ` Linus Walleij
2012-05-15 13:05 ` Dong Aisheng
2012-05-16 2:13 ` Shawn Guo
2012-05-16 6:50 ` Linus Walleij
2012-05-16 7:57 ` Dong Aisheng [this message]
2012-05-16 7:59 ` Linus Walleij
2012-05-16 15:35 ` Shawn Guo
2012-05-16 6:53 ` Linus Walleij
2012-05-15 7:49 Dong Aisheng
2012-05-16 7:45 ` Dong Aisheng
2012-05-16 7:49 ` Linus Walleij
2012-05-17 19:39 ` Stephen Warren
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=20120516075754.GG10347@shlinux2.ap.freescale.net \
--to=aisheng.dong@freescale.com \
--cc=B29396@freescale.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=r65073@freescale.com \
--cc=s.hauer@pengutronix.de \
--cc=swarren@wwwdotorg.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
Powered by JetHome