From: Conor Dooley <conor@kernel.org>
To: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Thierry Reding" <thierry.reding@gmail.com>,
"Conor Dooley" <conor.dooley@microchip.com>
Cc: Daire McNamara <daire.mcnamara@microchip.com>,
linux-kernel@vger.kernel.org, linux-pwm@vger.kernel.org,
linux-riscv@lists.infradead.org
Subject: [PATCH v13 2/2] MAINTAINERS: add pwm to PolarFire SoC entry
Date: Wed, 21 Dec 2022 11:29:13 +0000 [thread overview]
Message-ID: <20221221112912.147210-3-conor@kernel.org> (raw)
In-Reply-To: <20221221112912.147210-1-conor@kernel.org>
From: Conor Dooley <conor.dooley@microchip.com>
Add the newly introduced pwm driver to the existing PolarFire SoC entry.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 7729a30b9609..e459d539fdd1 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17979,6 +17979,7 @@ F: drivers/clk/microchip/clk-mpfs.c
F: drivers/i2c/busses/i2c-microchip-corei2c.c
F: drivers/mailbox/mailbox-mpfs.c
F: drivers/pci/controller/pcie-microchip-host.c
+F: drivers/pwm/pwm-microchip-core.c
F: drivers/reset/reset-mpfs.c
F: drivers/rtc/rtc-mpfs.c
F: drivers/soc/microchip/mpfs-sys-controller.c
--
2.38.1
next prev parent reply other threads:[~2022-12-21 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-21 11:29 [PATCH v13 0/2] Microchip Soft IP corePWM driver Conor Dooley
2022-12-21 11:29 ` [PATCH v13 1/2] pwm: add microchip soft ip " Conor Dooley
2023-01-10 22:48 ` Uwe Kleine-König
2023-01-11 0:15 ` Conor Dooley
2023-01-11 7:02 ` Uwe Kleine-König
2023-01-11 8:00 ` Conor Dooley
2023-01-11 9:15 ` Uwe Kleine-König
2023-01-11 9:24 ` Uwe Kleine-König
2023-01-12 12:01 ` Uwe Kleine-König
2023-01-12 15:10 ` Conor Dooley
2023-01-20 19:40 ` Conor Dooley
2023-02-13 12:45 ` Conor Dooley
2022-12-21 11:29 ` Conor Dooley [this message]
2023-01-10 22:50 ` [PATCH v13 2/2] MAINTAINERS: add pwm to PolarFire SoC entry Uwe Kleine-König
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=20221221112912.147210-3-conor@kernel.org \
--to=conor@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=daire.mcnamara@microchip.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@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).