From: Linus Walleij <linus.walleij@linaro.org>
To: Marco Felsch <m.felsch@pengutronix.de>, Lee Jones <lee.jones@linaro.org>
Cc: Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Support Opensource <support.opensource@diasemi.com>,
Adam Thomson <Adam.Thomson.Opensource@diasemi.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Sascha Hauer <kernel@pengutronix.de>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>
Subject: Re: [PATCH v3 0/3] Add DA9062 GPIO support
Date: Thu, 12 Dec 2019 15:56:18 +0100 [thread overview]
Message-ID: <CACRpkda0BCBj1LeFkWsjBPHi_4d-F+eu0tDLm9VrFbn1RyWkWA@mail.gmail.com> (raw)
In-Reply-To: <20191210095115.kxvm7elfkiw2kdem@pengutronix.de>
On Tue, Dec 10, 2019 at 10:51 AM Marco Felsch <m.felsch@pengutronix.de> wrote:
> gentle ping.
(...)
> > Marco Felsch (3):
> > dt-bindings: mfd: da9062: add gpio bindings
> > mfd: da9062: add support for the DA9062 GPIOs in the core
> > pinctrl: da9062: add driver support
I can merge this to the pinctrl subsystem but then I need
Lee's ACK on patches 1 & 2 as they are to the MFD subsystem
and I think he will want me to create an immutable branch too?
As Lee is not even on the To: line I think it is unlikely to happen,
so maybe repost, stating your request for his ACK?
Yours,
Linus Walleij
next prev parent reply other threads:[~2019-12-12 14:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 16:58 [PATCH v3 0/3] Add DA9062 GPIO support Marco Felsch
2019-11-29 16:58 ` [PATCH v3 1/3] dt-bindings: mfd: da9062: add gpio bindings Marco Felsch
2019-11-29 16:58 ` [PATCH v3 2/3] mfd: da9062: add support for the DA9062 GPIOs in the core Marco Felsch
2019-11-29 16:58 ` [PATCH v3 3/3] pinctrl: da9062: add driver support Marco Felsch
2019-12-10 9:51 ` [PATCH v3 0/3] Add DA9062 GPIO support Marco Felsch
2019-12-12 14:56 ` Linus Walleij [this message]
2019-12-12 15:48 ` Lee Jones
2019-12-12 15:49 ` Marco Felsch
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=CACRpkda0BCBj1LeFkWsjBPHi_4d-F+eu0tDLm9VrFbn1RyWkWA@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=lee.jones@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=m.felsch@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=support.opensource@diasemi.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 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).