From: Sergio Paracuellos <sergio.paracuellos@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Greg KH <gregkh@linuxfoundation.org>,
driverdev-devel@linuxdriverproject.org, juhosg@freemail.hu,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Rob Herring <robh+dt@kernel.org>, John Crispin <john@phrozen.org>,
NeilBrown <neil@brown.name>
Subject: Re: [PATCH v4 1/2] gpio: mediatek: add driver for MT7621
Date: Mon, 9 Jul 2018 15:28:50 +0200 [thread overview]
Message-ID: <20180709132850.GB2529@foobar> (raw)
In-Reply-To: <CACRpkdbWbFi-vzHqSu3T2iE89BJaQNCfZHVNvV7Crqq-TsLnmg@mail.gmail.com>
On Mon, Jul 09, 2018 at 01:45:22PM +0200, Linus Walleij wrote:
> On Thu, Jul 5, 2018 at 3:43 PM Sergio Paracuellos
> <sergio.paracuellos@gmail.com> wrote:
>
> > Add driver support for gpio of MT7621 SoC.
> >
> > Signed-off-by: Sergio Paracuellos <sergio.paracuellos@gmail.com>
> > Reviewed-by: NeilBrown <neil@brown.name>
>
> This is looking really good.
>
> Patch applied: anything remaining can surely be patched up
> in-tree.
>
Sound good, thanks.
Should I send a patch to remove the driver from staging or just
is removed by Greg? How is this achieved?
> > +/*
> > + * Copyright (C) 2009-2011 Gabor Juhos <juhosg@openwrt.org>
> > + * Copyright (C) 2013 John Crispin <blogic@openwrt.org>
> > + */
>
> All OpenWRT drivers are moving upstream and I like it :)
> Gabo and John wrote like 90% of them on their own :D
>
> > +#define GPIO_BANK_WIDE 0x04
>
> Nitpick: we usually call this "stride" rather than "wide".
> I changed it while applying the patch.
Thanks :-)
>
> Yours,
> Linus Walleij
Best regards,
Sergio Paracuellos
next prev parent reply other threads:[~2018-07-09 13:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-05 13:43 [PATCH v4 0/2] gpio: mediatek: driver for gpio chip in MT7621 SoC Sergio Paracuellos
2018-07-05 13:43 ` [PATCH v4 1/2] gpio: mediatek: add driver for MT7621 Sergio Paracuellos
2018-07-09 11:45 ` Linus Walleij
2018-07-09 13:28 ` Sergio Paracuellos [this message]
2018-07-09 13:30 ` Dan Carpenter
2018-07-09 16:07 ` Sergio Paracuellos
2018-07-05 13:43 ` [PATCH v4 2/2] dt-bindings: document gpio-mt7621 bindings Sergio Paracuellos
2018-07-05 23:11 ` Rob Herring
2018-07-09 11:37 ` Linus Walleij
2018-07-09 12:02 ` Sergio Paracuellos
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=20180709132850.GB2529@foobar \
--to=sergio.paracuellos@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=driverdev-devel@linuxdriverproject.org \
--cc=gregkh@linuxfoundation.org \
--cc=john@phrozen.org \
--cc=juhosg@freemail.hu \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=neil@brown.name \
--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).