From: Frank Li <Frank.Li@nxp.com>
To: frank.li@nxp.com, alexandre.belloni@bootlin.com,
miquel.raynal@bootlin.com
Cc: conor.culhane@silvaco.com, imx@lists.linux.dev,
linux-i3c@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 1/1] MAINTAINERS: I3C: Remove Conor Culhane from Silvaco driver maintainer
Date: Tue, 4 Feb 2025 11:11:51 -0500 [thread overview]
Message-ID: <20250204161151.2179596-1-Frank.Li@nxp.com> (raw)
Conor Culhane's email address (conor.culhane@silvaco.com) is no longer
accessible, and there has been no activity from him on
https://lore.kernel.org/linux-i3c/ in the past two years.
To avoid email delivery failure messages when sending patches to the I3C
mailing list, remove him from the Maintainers section and move him to the
credits.
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
CREDITS | 4 ++++
MAINTAINERS | 1 -
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/CREDITS b/CREDITS
index 324428ad37e83..89a86bebd9b58 100644
--- a/CREDITS
+++ b/CREDITS
@@ -855,6 +855,10 @@ N: John Crispin
E: john@phrozen.org
D: MediaTek MT7623 Gigabit ethernet support
+N: Conor Culhane
+E: conor.culhane@silvaco.com
+D: Silvaco I3C master driver
+
N: Laurence Culhane
E: loz@holmes.demon.co.uk
D: Wrote the initial alpha SLIP code
diff --git a/MAINTAINERS b/MAINTAINERS
index 51e5f43c63544..40d1b7ec30fde 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -21661,7 +21661,6 @@ F: drivers/video/fbdev/sm712*
SILVACO I3C DUAL-ROLE MASTER
M: Miquel Raynal <miquel.raynal@bootlin.com>
-M: Conor Culhane <conor.culhane@silvaco.com>
L: linux-i3c@lists.infradead.org (moderated for non-subscribers)
S: Maintained
F: Documentation/devicetree/bindings/i3c/silvaco,i3c-master.yaml
--
2.34.1
next reply other threads:[~2025-02-04 16:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 16:11 Frank Li [this message]
2025-02-04 16:53 ` [PATCH 1/1] MAINTAINERS: I3C: Remove Conor Culhane from Silvaco driver maintainer Miquel Raynal
2025-02-20 22:09 ` Alexandre Belloni
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=20250204161151.2179596-1-Frank.Li@nxp.com \
--to=frank.li@nxp.com \
--cc=alexandre.belloni@bootlin.com \
--cc=conor.culhane@silvaco.com \
--cc=imx@lists.linux.dev \
--cc=linux-i3c@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miquel.raynal@bootlin.com \
/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