mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sander Vanheule <sander@svanheule.net>
To: linux-gpio@vger.kernel.org, Bartosz Golaszewski <brgl@bgdev.pl>
Cc: Linus Walleij <linus.walleij@linaro.org>,
	linux-kernel@vger.kernel.org, Bert Vermeulen <bert@biot.com>,
	Sander Vanheule <sander@svanheule.net>
Subject: [PATCH v1 2/2] MAINTAINERS: add info for Realtek Otto GPIO
Date: Fri, 22 Jul 2022 10:19:17 +0200	[thread overview]
Message-ID: <d162ec319ff67b77e375c2f2aa24eb297325d7c2.1658477809.git.sander@svanheule.net> (raw)
In-Reply-To: <cover.1658477809.git.sander@svanheule.net>

Add an entry with the files for the Realtek Otto GPIO driver with myself
as maintainer. I am already listed as maintainer in the device tree
binding itself, but the driver had no explicit maintainer info yet.

Signed-off-by: Sander Vanheule <sander@svanheule.net>
---
 MAINTAINERS | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git a/MAINTAINERS b/MAINTAINERS
index 651616ed8ae2..b173f9e3ee3c 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17009,6 +17009,13 @@ S:	Maintained
 F:	include/sound/rt*.h
 F:	sound/soc/codecs/rt*
 
+REALTEK OTTO GPIO
+M:	Sander Vanheule <sander@svanheule.net>
+L:	linux-gpio@vger.kernel.org
+S:	Maintained
+F:	Documentation/devicetree/bindings/gpio/realtek,otto-gpio.yaml
+F:	drivers/gpio/gpio-realtek-otto.c
+
 REALTEK OTTO WATCHDOG
 M:	Sander Vanheule <sander@svanheule.net>
 L:	linux-watchdog@vger.kernel.org
-- 
2.36.1


      parent reply	other threads:[~2022-07-22  8:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22  8:19 [PATCH v1 0/2] gpio: update Realtek Otto documenentation Sander Vanheule
2022-07-22  8:19 ` [PATCH v1 1/2] gpio: realtek-otto: amend ctrl struct docs Sander Vanheule
2022-07-23  9:52   ` Sander Vanheule
2022-07-22  8:19 ` Sander Vanheule [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=d162ec319ff67b77e375c2f2aa24eb297325d7c2.1658477809.git.sander@svanheule.net \
    --to=sander@svanheule.net \
    --cc=bert@biot.com \
    --cc=brgl@bgdev.pl \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®