From: Conor Dooley <conor.dooley@microchip.com>
To: <wsa@kernel.org>, <linux-i2c@vger.kernel.org>
Cc: <ben.dooks@codethink.co.uk>, <linux-kernel@vger.kernel.org>,
<linux-riscv@lists.infradead.org>, <daire.mcnamara@microchip.com>,
<conor.dooley@microchip.com>
Subject: [PATCH v6 2/2] MAINTAINERS: add the polarfire soc's i2c driver
Date: Tue, 21 Jun 2022 08:42:39 +0100 [thread overview]
Message-ID: <20220621074238.957177-2-conor.dooley@microchip.com> (raw)
In-Reply-To: <20220621074238.957177-1-conor.dooley@microchip.com>
Add the newly added i2c controller driver to the existing entry for
PolarFire SoC.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
---
New in v6.
FYI: I have several maintainers updates in flight - usb, pwm, spi
of which some will be in 5.20 & clk/hwrng/pci that are likely to
go into 5.19-rcN.
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index a6d3bd9d2a8d..90de65041863 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -17141,6 +17141,7 @@ M: Conor Dooley <conor.dooley@microchip.com>
L: linux-riscv@lists.infradead.org
S: Supported
F: arch/riscv/boot/dts/microchip/
+F: drivers/i2c/busses/i2c-microchip-core.c
F: drivers/mailbox/mailbox-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-06-21 7:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-21 7:42 [PATCH v6 1/2] i2c: add support for microchip fpga i2c controllers Conor Dooley
2022-06-21 7:42 ` Conor Dooley [this message]
2022-07-06 7:21 ` [PATCH v6 2/2] MAINTAINERS: add the polarfire soc's i2c driver Wolfram Sang
2022-07-06 7:41 ` Conor.Dooley
2022-07-06 7:19 ` [PATCH v6 1/2] i2c: add support for microchip fpga i2c controllers Wolfram Sang
2022-07-06 8:03 ` Conor.Dooley
2022-07-06 10:32 ` Wolfram Sang
2022-07-06 10:50 ` 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=20220621074238.957177-2-conor.dooley@microchip.com \
--to=conor.dooley@microchip.com \
--cc=ben.dooks@codethink.co.uk \
--cc=daire.mcnamara@microchip.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=wsa@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