From: Linus Walleij <linus.walleij@linaro.org>
To: Michael Walle <michael@walle.cc>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"open list:GPIO SUBSYSTEM" <linux-gpio@vger.kernel.org>,
Bartosz Golaszewski <bgolaszewski@baylibre.com>,
Mark Brown <broonie@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@intel.com>,
Andy Shevchenko <andy.shevchenko@gmail.com>
Subject: Re: [PATCH v6 0/3] gpio: generic regmap implementation
Date: Wed, 3 Jun 2020 10:50:30 +0200 [thread overview]
Message-ID: <CACRpkdbAeF6bVDvcMAXguFpHeEnq7DnmWswRnXjByNkH7t3Bhg@mail.gmail.com> (raw)
In-Reply-To: <20200528145845.31436-1-michael@walle.cc>
On Thu, May 28, 2020 at 4:59 PM Michael Walle <michael@walle.cc> wrote:
> This series is a split off of the sl28cpld series:
> https://lore.kernel.org/linux-gpio/20200423174543.17161-1-michael@walle.cc/
>
> I wasn't sure if I should also include the gpiochip_irqchip_add_domain()
> patch here. So feel free to skip it. OTOH if you use interrupts with
> gpio-regmap it is quite handy.
>
> For an actual user see the patch 11/16 ("gpio: add support for the sl28cpld
> GPIO controller") of the series above.
Patches applied as some of the last stuff before sending my pull
requests :)
Let's work with this as a base, and thanks a *LOT* for your work
so far!
Yours,
Linus Walleij
prev parent reply other threads:[~2020-06-03 8:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-28 14:58 [PATCH v6 0/3] gpio: generic regmap implementation Michael Walle
2020-05-28 14:58 ` [PATCH v6 1/3] gpiolib: Introduce gpiochip_irqchip_add_domain() Michael Walle
2020-05-28 14:58 ` [PATCH v6 2/3] gpio: add a reusable generic gpio_chip using regmap Michael Walle
[not found] ` <adb4eba6-c6c4-a403-dead-1951050eec26@linux.intel.com>
2020-05-28 17:03 ` Michael Walle
2020-05-28 18:15 ` Pierre-Louis Bossart
2020-05-28 14:58 ` [PATCH v6 3/3] MAINTAINERS: Add gpio regmap section Michael Walle
2020-05-28 15:11 ` [PATCH v6 0/3] gpio: generic regmap implementation Andy Shevchenko
2020-06-03 8:50 ` Linus Walleij [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=CACRpkdbAeF6bVDvcMAXguFpHeEnq7DnmWswRnXjByNkH7t3Bhg@mail.gmail.com \
--to=linus.walleij@linaro.org \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=pierre-louis.bossart@intel.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).