From: Marco Felsch <m.felsch@pengutronix.de>
To: linus.walleij@linaro.org, bgolaszewski@baylibre.com,
robh+dt@kernel.org, support.opensource@diasemi.com,
Adam.Thomson.Opensource@diasemi.com
Cc: devicetree@vger.kernel.org, kernel@pengutronix.de,
linux-gpio@vger.kernel.org
Subject: Re: [PATCH v3 0/3] Add DA9062 GPIO support
Date: Tue, 10 Dec 2019 10:51:15 +0100 [thread overview]
Message-ID: <20191210095115.kxvm7elfkiw2kdem@pengutronix.de> (raw)
In-Reply-To: <20191129165817.20426-1-m.felsch@pengutronix.de>
Hi,
gentle ping.
Regards,
Marco
On 19-11-29 17:58, Marco Felsch wrote:
> Hi,
>
> this update address all comments made on [1], for further details see
> the patch based changelog.
>
> [1] https://patchwork.ozlabs.org/cover/1201549/
>
> 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
>
> .../devicetree/bindings/mfd/da9062.txt | 10 +
> MAINTAINERS | 1 +
> drivers/mfd/da9062-core.c | 16 +-
> drivers/pinctrl/Kconfig | 12 +
> drivers/pinctrl/Makefile | 1 +
> drivers/pinctrl/pinctrl-da9062.c | 297 ++++++++++++++++++
> 6 files changed, 336 insertions(+), 1 deletion(-)
> create mode 100644 drivers/pinctrl/pinctrl-da9062.c
>
> --
> 2.20.1
>
next prev parent reply other threads:[~2019-12-10 9:51 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 ` Marco Felsch [this message]
2019-12-12 14:56 ` [PATCH v3 0/3] Add DA9062 GPIO support Linus Walleij
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=20191210095115.kxvm7elfkiw2kdem@pengutronix.de \
--to=m.felsch@pengutronix.de \
--cc=Adam.Thomson.Opensource@diasemi.com \
--cc=bgolaszewski@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--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).