From: B35083@freescale.com (Lu Jingchang-B35083)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 1/2] pinctrl: add MVF600 pinctrl driver
Date: Tue, 21 May 2013 07:56:21 +0000 [thread overview]
Message-ID: <B56CDBE15CE27145A4B77D2D24263E851CBBA4@039-SN1MPN1-003.039d.mgd.msft.net> (raw)
In-Reply-To: <CAAQ0ZWSZeqOEceN-KmDS4_BT27_4xCYjfFMj8sHkEonOXaoF_g@mail.gmail.com>
>-----Original Message-----
>From: Shawn Guo [mailto:shawn.guo at linaro.org]
>Sent: Monday, May 20, 2013 11:52 AM
>To: Lu Jingchang-B35083
>Cc: linux-arm-kernel; Linus Walleij; Sascha Hauer
>Subject: Re: [PATCH v3 1/2] pinctrl: add MVF600 pinctrl driver
>
>On 20 May 2013 11:32, Shawn Guo <shawn.guo@linaro.org> wrote:
>>> +static struct imx_pinctrl_soc_info mvf600_pinctrl_info = {
>>> + .pins = mvf600_pinctrl_pads,
>>> + .npins = ARRAY_SIZE(mvf600_pinctrl_pads),
>>> + .flags = ZERO_OFFSET_VALID | SHARE_MUX_CONF_REG,
>>
>> The flags should be introduced in the same patch where they are used
>> in the first place.
>>
>I just found what you need to do is just to reverse the patch order,
>having this patch be the second one.
>
[Lu Jingchang-B35083]
I see you have Acked [PATCH v3 2/2] pinctrl: imx: add MVF600 support to imx pinctrl framework, do I need resend it as the first one. Thanks!
next prev parent reply other threads:[~2013-05-21 7:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 6:20 [PATCH v3 1/2] pinctrl: add MVF600 pinctrl driver Jingchang Lu
2013-05-16 6:20 ` [PATCH v3 2/2] pinctrl: imx: add MVF600 support to imx pinctrl framework Jingchang Lu
2013-05-20 4:01 ` Shawn Guo
2013-05-24 7:54 ` Linus Walleij
2013-05-20 3:32 ` [PATCH v3 1/2] pinctrl: add MVF600 pinctrl driver Shawn Guo
2013-05-20 3:51 ` Shawn Guo
2013-05-21 7:56 ` Lu Jingchang-B35083 [this message]
2013-05-22 3:24 ` Shawn Guo
2013-05-24 8:55 ` Linus Walleij
2013-05-24 9:25 ` Lu Jingchang-B35083
2013-05-24 11:08 ` Linus Walleij
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=B56CDBE15CE27145A4B77D2D24263E851CBBA4@039-SN1MPN1-003.039d.mgd.msft.net \
--to=b35083@freescale.com \
--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.