From: Shawn Guo <shawnguo@kernel.org>
To: Alonso Adrian <aalonso@freescale.com>
Cc: Markus Pargmann <mpa@pengutronix.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"shawn.guo@linaro.org" <shawn.guo@linaro.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"lznuaa@gmail.com" <lznuaa@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Li Frank <Frank.Li@freescale.com>,
Nitin Garg <nitin.garg@freescale.com>,
Huang Anson <Anson.Huang@freescale.com>,
"linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
Yibin Gong <yibin.gong@freescale.com>
Subject: Re: [PATCH v5 4/7] pinctrl: freescale: imx: allow mux_reg offset zero
Date: Fri, 25 Sep 2015 13:59:02 -0700 [thread overview]
Message-ID: <20150925205902.GZ3529@tiger> (raw)
In-Reply-To: <BN3PR03MB150994443644800594BE9BA2A8420@BN3PR03MB1509.namprd03.prod.outlook.com>
On Fri, Sep 25, 2015 at 07:16:49PM +0000, Alonso Adrian wrote:
> > Ah, sorry, I'm screwed on the previous review. So we still need the flag
> > ZERO_OFFSET_VALID to convert invalid 0 mux_reg to -1.
> >
> > @Adrian,
> >
> > Will the following change just work for you?
> @Shawn, yes the change will work, do you want me to prepare a new patch series?
Most of the patches in this series will go to Linus. So that's his
call, but I suggest you resend.
Shawn
WARNING: multiple messages have this Message-ID (diff)
From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v5 4/7] pinctrl: freescale: imx: allow mux_reg offset zero
Date: Fri, 25 Sep 2015 13:59:02 -0700 [thread overview]
Message-ID: <20150925205902.GZ3529@tiger> (raw)
In-Reply-To: <BN3PR03MB150994443644800594BE9BA2A8420@BN3PR03MB1509.namprd03.prod.outlook.com>
On Fri, Sep 25, 2015 at 07:16:49PM +0000, Alonso Adrian wrote:
> > Ah, sorry, I'm screwed on the previous review. So we still need the flag
> > ZERO_OFFSET_VALID to convert invalid 0 mux_reg to -1.
> >
> > @Adrian,
> >
> > Will the following change just work for you?
> @Shawn, yes the change will work, do you want me to prepare a new patch series?
Most of the patches in this series will go to Linus. So that's his
call, but I suggest you resend.
Shawn
next prev parent reply other threads:[~2015-09-25 20:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-24 20:53 [PATCH v5 1/7] pinctrl: freescale: imx: fix system crash if enable two pinctl instances Adrian Alonso
2015-09-24 20:53 ` Adrian Alonso
2015-09-24 20:53 ` [PATCH v5 2/7] ARM: dts: imx: imx7d add iomuxc lpsr device node Adrian Alonso
2015-09-24 20:53 ` Adrian Alonso
2015-09-24 20:53 ` [PATCH v5 3/7] ARM: dts: imx: imx7d-sbd add iomuxc-lpsr hoggrp-2 pads Adrian Alonso
2015-09-24 20:53 ` Adrian Alonso
2015-09-25 10:49 ` Markus Pargmann
2015-09-25 10:49 ` Markus Pargmann
2015-09-25 17:17 ` Shawn Guo
2015-09-25 17:17 ` Shawn Guo
2015-09-24 20:54 ` [PATCH v5 4/7] pinctrl: freescale: imx: allow mux_reg offset zero Adrian Alonso
2015-09-24 20:54 ` Adrian Alonso
2015-09-25 10:47 ` Markus Pargmann
2015-09-25 10:47 ` Markus Pargmann
2015-09-25 19:07 ` Shawn Guo
2015-09-25 19:07 ` Shawn Guo
2015-09-25 19:16 ` Alonso Adrian
2015-09-25 19:16 ` Alonso Adrian
2015-09-25 20:59 ` Shawn Guo [this message]
2015-09-25 20:59 ` Shawn Guo
2015-09-24 20:54 ` [PATCH v5 5/7] pinctrl: freescale: imx: add shared input select reg support Adrian Alonso
2015-09-24 20:54 ` Adrian Alonso
2015-09-24 20:54 ` [PATCH v5 6/7] pinctrl: freescale: imx7d: support iomux lpsr controller Adrian Alonso
2015-09-24 20:54 ` Adrian Alonso
2015-09-24 20:54 ` [PATCH v5 7/7] pinctrl: freescale: imx: imx7d iomuxc-lpsr devicetree bindings Adrian Alonso
2015-09-24 20:54 ` Adrian Alonso
2015-09-25 16:50 ` [PATCH v5 1/7] pinctrl: freescale: imx: fix system crash if enable two pinctl instances Linus Walleij
2015-09-25 16:50 ` Linus Walleij
[not found] ` <1443128043-21063-1-git-send-email-aalonso-KZfg59tc24xl57MIdRCFDg@public.gmane.org>
2015-09-25 19:09 ` Shawn Guo
2015-09-25 19:09 ` Shawn Guo
2015-10-02 12:19 ` Linus Walleij
2015-10-02 12:19 ` 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=20150925205902.GZ3529@tiger \
--to=shawnguo@kernel.org \
--cc=Anson.Huang@freescale.com \
--cc=Frank.Li@freescale.com \
--cc=aalonso@freescale.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-gpio@vger.kernel.org \
--cc=lznuaa@gmail.com \
--cc=mpa@pengutronix.de \
--cc=nitin.garg@freescale.com \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=yibin.gong@freescale.com \
/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.