From: Conor Dooley <conor.dooley@microchip.com> To: <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com> Cc: <daire.mcnamara@microchip.com>, <lewis.hanly@microchip.com>, <conor.dooley@microchip.com>, <linux-kernel@vger.kernel.org>, <linux-rtc@vger.kernel.org>, <linux-riscv@lists.infradead.org> Subject: [PATCH v3 2/2] MAINTAINERS: add PolarFire SoC's RTC Date: Mon, 16 May 2022 09:28:39 +0100 [thread overview] Message-ID: <20220516082838.3717982-3-conor.dooley@microchip.com> (raw) In-Reply-To: <20220516082838.3717982-1-conor.dooley@microchip.com> Add an entry for PolarFire SoC's RTC drver to the existing support for PolarFire SoC. Signed-off-by: Conor Dooley <conor.dooley@microchip.com> --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index e8c52d0192a6..625d735f6a24 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -16952,6 +16952,7 @@ L: linux-riscv@lists.infradead.org S: Supported F: arch/riscv/boot/dts/microchip/ F: drivers/mailbox/mailbox-mpfs.c +F: drivers/rtc/rtc-mpfs.c F: drivers/soc/microchip/ F: include/soc/microchip/mpfs.h -- 2.36.1
WARNING: multiple messages have this Message-ID (diff)
From: Conor Dooley <conor.dooley@microchip.com> To: <a.zummo@towertech.it>, <alexandre.belloni@bootlin.com> Cc: <daire.mcnamara@microchip.com>, <lewis.hanly@microchip.com>, <conor.dooley@microchip.com>, <linux-kernel@vger.kernel.org>, <linux-rtc@vger.kernel.org>, <linux-riscv@lists.infradead.org> Subject: [PATCH v3 2/2] MAINTAINERS: add PolarFire SoC's RTC Date: Mon, 16 May 2022 09:28:39 +0100 [thread overview] Message-ID: <20220516082838.3717982-3-conor.dooley@microchip.com> (raw) In-Reply-To: <20220516082838.3717982-1-conor.dooley@microchip.com> Add an entry for PolarFire SoC's RTC drver to the existing support for PolarFire SoC. Signed-off-by: Conor Dooley <conor.dooley@microchip.com> --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index e8c52d0192a6..625d735f6a24 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -16952,6 +16952,7 @@ L: linux-riscv@lists.infradead.org S: Supported F: arch/riscv/boot/dts/microchip/ F: drivers/mailbox/mailbox-mpfs.c +F: drivers/rtc/rtc-mpfs.c F: drivers/soc/microchip/ F: include/soc/microchip/mpfs.h -- 2.36.1 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-05-16 8:31 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-05-16 8:28 [PATCH v3 0/2] rtc: microchip: Add driver for PolarFire SoC Conor Dooley 2022-05-16 8:28 ` Conor Dooley 2022-05-16 8:28 ` [PATCH v3 1/2] rtc: Add driver for Microchip " Conor Dooley 2022-05-16 8:28 ` Conor Dooley 2022-05-17 21:09 ` Alexandre Belloni 2022-05-17 21:09 ` Alexandre Belloni 2022-05-17 21:37 ` Conor.Dooley 2022-05-17 21:37 ` Conor.Dooley 2022-05-30 7:07 ` Pavel Machek 2022-05-30 7:07 ` Pavel Machek 2022-05-30 13:27 ` Geert Uytterhoeven 2022-05-30 13:27 ` Geert Uytterhoeven 2022-05-16 8:28 ` Conor Dooley [this message] 2022-05-16 8:28 ` [PATCH v3 2/2] MAINTAINERS: add PolarFire SoC's RTC 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=20220516082838.3717982-3-conor.dooley@microchip.com \ --to=conor.dooley@microchip.com \ --cc=a.zummo@towertech.it \ --cc=alexandre.belloni@bootlin.com \ --cc=daire.mcnamara@microchip.com \ --cc=lewis.hanly@microchip.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-riscv@lists.infradead.org \ --cc=linux-rtc@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.