From: Martin Schiller <mschiller@tdt.de>
To: Jonas Gorski <jogo@openwrt.org>
Cc: "linux-gpio@vger.kernel.org" <linux-gpio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
MIPS Mailing List <linux-mips@linux-mips.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Ralf Baechle <ralf@linux-mips.org>,
John Crispin <blogic@openwrt.org>,
Hauke Mehrtens <hauke@hauke-m.de>,
"daniel.schwierzeck@gmail.com" <daniel.schwierzeck@gmail.com>
Subject: RE: [PATCH v2 4/4] pinctrl/lantiq: fix up pinmux
Date: Thu, 26 Nov 2015 06:40:18 +0000 [thread overview]
Message-ID: <c9edbc5eafed4639983f8bcefe8e872e@TDT-MS.TDTNET.local> (raw)
In-Reply-To: <CAOiHx=moeuw-qWdq0YVzVD3dv0Zq+3rxb2tAKV1Hiz35y4+7DQ@mail.gmail.com>
On 11/25/2015 at 11:40 AM, Jonas Gorski wrote:
> Hi
>
> On Wed, Nov 25, 2015 at 11:18 AM, Martin Schiller <mschiller@tdt.de>
> wrote:
> > From: John Crispin <blogic@openwrt.org>
> >
> > This patch is included in the openwrt patchset for several years now
> and needs
> > to go upstream as well. It includes the following changes:
> > 1. Fix up inline function call to xway_mux_apply
>
> This really needs an explanation what is being fixed here.
I hope John - as the original author of this patch - can explain
why this change is necessary.
>
> > 2. Fix GPIO Setup of GPIO Port3
>
> This change looks fine.
>
> > 3. Implement gpio_chip.to_irq
>
> These are three different changes (two fixes, one new feature) and
> therefore should be split up into three patches.
As I'm not the author of this patch, I decided to leave it as it is.
But per se you are right, it would be better to split it up.
>
> > Signed-off-by: John Crispin <blogic@openwrt.org>
> > Signed-off-by: Martin Schiller <mschiller@tdt.de>
> > ---
>
> Also please provide a changelog for your patches here.
OK.
>
> > drivers/pinctrl/pinctrl-xway.c | 28 ++++++++++++++++++++++++++--
> > 1 file changed, 26 insertions(+), 2 deletions(-)
> >
>
>
> Jonas
Martin
next prev parent reply other threads:[~2015-11-26 6:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-25 10:18 [PATCH v2 1/4] pinctrl/lantiq: updating devicetree binding description Martin Schiller
2015-11-25 10:18 ` [PATCH v2 2/4] pinctrl/lantiq: introduce new dedicated devicetree bindings Martin Schiller
2015-11-25 10:18 ` [PATCH v2 3/4] pinctrl/lantiq: update devicetree binding in dts file Martin Schiller
2015-11-25 10:18 ` [PATCH v2 4/4] pinctrl/lantiq: fix up pinmux Martin Schiller
2015-11-25 10:40 ` Jonas Gorski
2015-11-26 6:40 ` Martin Schiller [this message]
2015-11-26 7:04 ` John Crispin
2015-11-26 7:15 ` Martin Schiller
2015-11-26 7:20 ` John Crispin
2015-11-26 7:47 ` Martin Schiller
2015-11-25 20:05 ` [PATCH v2 1/4] pinctrl/lantiq: updating devicetree binding description Rob Herring
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=c9edbc5eafed4639983f8bcefe8e872e@TDT-MS.TDTNET.local \
--to=mschiller@tdt.de \
--cc=blogic@openwrt.org \
--cc=daniel.schwierzeck@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=hauke@hauke-m.de \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jogo@openwrt.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-mips@linux-mips.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=ralf@linux-mips.org \
--cc=robh+dt@kernel.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).