devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dong Aisheng <aisheng.dong@freescale.com>
To: Dong Aisheng-B29396 <B29396@freescale.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"devicetree-discuss@lists.ozlabs.org"
	<devicetree-discuss@lists.ozlabs.org>,
	"linus.walleij@stericsson.com" <linus.walleij@stericsson.com>,
	"swarren@wwwdotorg.org" <swarren@wwwdotorg.org>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	Guo Shawn-R65073 <r65073@freescale.com>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH 1/2] pinctrl: pinctrl-imx: add imx53 pinctrl driver
Date: Wed, 16 May 2012 15:45:31 +0800	[thread overview]
Message-ID: <20120516074530.GE10347@shlinux2.ap.freescale.net> (raw)
In-Reply-To: <1337068143-15579-1-git-send-email-b29396@freescale.com>

Hi Linus,

On Tue, May 15, 2012 at 03:49:02PM +0800, Dong Aisheng-B29396 wrote:
> From: Dong Aisheng <dong.aisheng@linaro.org>
> 
> Signed-off-by: Dong Aisheng <dong.aisheng@linaro.org>
> ---
> ChangeLog v1->v2:
> * change PIN_FUNC_ID base in binding doc to 0 from 1.
I just checked your tree and it seems you merged the v1 series.
Can you merge this v2 instead?
I'm sorry that this patch title missed a v2 flag which caused you some
inconvenience.

Regards
Dong Aisheng

  parent reply	other threads:[~2012-05-16  7:45 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15  7:49 [PATCH 1/2] pinctrl: pinctrl-imx: add imx53 pinctrl driver Dong Aisheng
2012-05-15  7:49 ` [PATCH 2/2] pinctrl: pinctrl-imx: add imx51 " Dong Aisheng
2012-05-16  7:45 ` Dong Aisheng [this message]
2012-05-16  7:49   ` [PATCH 1/2] pinctrl: pinctrl-imx: add imx53 " 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=20120516074530.GE10347@shlinux2.ap.freescale.net \
    --to=aisheng.dong@freescale.com \
    --cc=B29396@freescale.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=kernel@pengutronix.de \
    --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;
as well as URLs for NNTP newsgroup(s).