From: Conor Dooley <conor@kernel.org>
To: linux-gpio@vger.kernel.org
Cc: conor@kernel.org, Conor Dooley <conor.dooley@microchip.com>,
Daire McNamara <daire.mcnamara@microchip.com>,
Linus Walleij <linus.walleij@linaro.org>,
Bartosz Golaszewski <brgl@bgdev.pl>,
linux-kernel@vger.kernel.org
Subject: [PATCH v1 2/2] MAINTAINERS: add gpio driver to PolarFire entry
Date: Thu, 7 Nov 2024 10:33:41 +0000 [thread overview]
Message-ID: <20241107-chewable-spoiler-3e7dd58d3e8d@spud> (raw)
In-Reply-To: <20241107-avatar-clapper-93eb34ad0e0c@spud>
From: Conor Dooley <conor.dooley@microchip.com>
Lewis' original GPIO driver patchset didn't add MAINTAINERS coverage of
the driver and I forgot to add it to the existing entry. Make up for the
minimal amount of lost time.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 1d6aca7ffc0a..e73a0b848bf2 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -19837,6 +19837,7 @@ F: arch/riscv/boot/dts/microchip/
F: drivers/char/hw_random/mpfs-rng.c
F: drivers/clk/microchip/clk-mpfs*.c
F: drivers/firmware/microchip/mpfs-auto-update.c
+F: drivers/gpio/gpio-mpfs.c
F: drivers/i2c/busses/i2c-microchip-corei2c.c
F: drivers/mailbox/mailbox-mpfs.c
F: drivers/pci/controller/plda/pcie-microchip-host.c
--
2.45.2
next prev parent reply other threads:[~2024-11-07 10:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-07 10:33 [PATCH v1 0/2] polarfire gpio driver follow-ups Conor Dooley
2024-11-07 10:33 ` [PATCH v1 1/2] gpio: mpfs: add CoreGPIO support Conor Dooley
2024-11-10 19:08 ` Bartosz Golaszewski
2024-11-07 10:33 ` Conor Dooley [this message]
2024-11-10 19:10 ` (subset) [PATCH v1 0/2] polarfire gpio driver follow-ups Bartosz Golaszewski
2024-11-11 9:24 ` Conor Dooley
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=20241107-chewable-spoiler-3e7dd58d3e8d@spud \
--to=conor@kernel.org \
--cc=brgl@bgdev.pl \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--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