From: Michael Walle <michael@walle.cc>
To: linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Cc: Linus Walleij <linus.walleij@linaro.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>,
Michael Walle <michael@walle.cc>
Subject: [PATCH v6 3/3] MAINTAINERS: Add gpio regmap section
Date: Thu, 28 May 2020 16:58:45 +0200 [thread overview]
Message-ID: <20200528145845.31436-4-michael@walle.cc> (raw)
In-Reply-To: <20200528145845.31436-1-michael@walle.cc>
Add myself as a reviewer for the gpio regmap.
Signed-off-by: Michael Walle <michael@walle.cc>
---
MAINTAINERS | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 3a003f310574..f3458debb0c9 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7340,6 +7340,12 @@ S: Maintained
F: drivers/gpio/gpio-mockup.c
F: tools/testing/selftests/gpio/
+GPIO REGMAP
+R: Michael Walle <michael@walle.cc>
+S: Maintained
+F: drivers/gpio/gpio-regmap.c
+F: include/linux/gpio/regmap.h
+
GPIO SUBSYSTEM
M: Linus Walleij <linus.walleij@linaro.org>
M: Bartosz Golaszewski <bgolaszewski@baylibre.com>
--
2.20.1
next prev parent reply other threads:[~2020-05-28 14:59 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 ` Michael Walle [this message]
2020-05-28 15:11 ` [PATCH v6 0/3] gpio: generic regmap implementation Andy Shevchenko
2020-06-03 8:50 ` Linus Walleij
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=20200528145845.31436-4-michael@walle.cc \
--to=michael@walle.cc \
--cc=andy.shevchenko@gmail.com \
--cc=bgolaszewski@baylibre.com \
--cc=broonie@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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).