From: Bartosz Golaszewski <brgl@bgdev.pl>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Linus Walleij <linus.walleij@linaro.org>,
kernel@pengutronix.de, Serge Semin <fancer.lancer@gmail.com>
Subject: Re: [PATCH v5 0/2] gpio: Add gpio-latch driver
Date: Tue, 25 Oct 2022 11:39:40 +0200 [thread overview]
Message-ID: <CAMRc=MfqvNvq7RLbWivZj7Q4fBBLEAWFHU0Wq+u-086ehK-jLA@mail.gmail.com> (raw)
In-Reply-To: <20221007114647.2723457-1-s.hauer@pengutronix.de>
On Fri, Oct 7, 2022 at 1:47 PM Sascha Hauer <s.hauer@pengutronix.de> wrote:
>
> This series includes the changes requested by Serge Semin for v4.
>
> Sascha
>
> Sascha Hauer (2):
> gpio: Add gpio latch driver
> dt-bindings: gpio: Add gpio-latch binding document
>
> .../devicetree/bindings/gpio/gpio-latch.yaml | 94 ++++++++
> drivers/gpio/Kconfig | 6 +
> drivers/gpio/Makefile | 1 +
> drivers/gpio/gpio-latch.c | 220 ++++++++++++++++++
> 4 files changed, 321 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpio/gpio-latch.yaml
> create mode 100644 drivers/gpio/gpio-latch.c
>
> --
> 2.30.2
>
I reversed the order of the patches, fixed the strange formatting of
struct of_device_id and queued the series.
Bartosz
prev parent reply other threads:[~2022-10-25 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-07 11:46 [PATCH v5 0/2] gpio: Add gpio-latch driver Sascha Hauer
2022-10-07 11:46 ` [PATCH v5 1/2] gpio: Add gpio latch driver Sascha Hauer
2022-10-07 16:29 ` Serge Semin
2022-10-17 8:50 ` Linus Walleij
2022-10-07 11:46 ` [PATCH v5 2/2] dt-bindings: gpio: Add gpio-latch binding document Sascha Hauer
2022-10-07 16:33 ` Serge Semin
2022-10-17 8:51 ` Linus Walleij
2022-10-25 9:39 ` Bartosz Golaszewski [this message]
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='CAMRc=MfqvNvq7RLbWivZj7Q4fBBLEAWFHU0Wq+u-086ehK-jLA@mail.gmail.com' \
--to=brgl@bgdev.pl \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
/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).