From: Brendan Higgins <brendanhiggins@google.com>
To: tommy_huang@aspeedtech.com, benh@kernel.crashing.org,
joel@jms.id.au, andi.shyti@kernel.org,
andrew@codeconstruct.com.au, wsa@kernel.org,
ryan_chen@aspeedtech.com
Cc: linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
BMC-SW@aspeedtech.com, brendan.higgins@linux.dev,
Brendan Higgins <brendanhiggins@google.com>
Subject: [RFC v1] MAINTAINERS: transfer i2c-aspeed maintainership from Brendan to Ryan
Date: Fri, 15 Nov 2024 04:43:03 +0000 [thread overview]
Message-ID: <20241115044303.50877-1-brendanhiggins@google.com> (raw)
Remove Brendan Higgins <brendanhiggins@google.com> from i2c-aspeed entry
and replace with Ryan Chen <ryan_chen@aspeedtech.com>.
Signed-off-by: Brendan Higgins <brendanhiggins@google.com>
---
I am leaving Google and am going through and cleaning up my @google.com
address in the relevant places. I was just going to remove myself from
the ASPEED I2C DRIVER since I haven't been paying attention to it, but
then I saw Ryan is adding a file for the I2C functions on 2600, which
made my think: Should I replace myself with Ryan as the maintainer?
I see that I am the only person actually listed as the maintainer at the
moment, and I don't want to leave this in an unmaintained state. What
does everyone think? Are we cool with Ryan as the new maintainer?
---
MAINTAINERS | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index b878ddc99f94e..e7fba34947f5f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -2195,7 +2195,7 @@ F: drivers/mmc/host/usdhi6rol0.c
F: drivers/pinctrl/pinctrl-artpec*
ARM/ASPEED I2C DRIVER
-M: Brendan Higgins <brendanhiggins@google.com>
+M: Ryan Chen <ryan_chen@aspeedtech.com>
R: Benjamin Herrenschmidt <benh@kernel.crashing.org>
R: Joel Stanley <joel@jms.id.au>
L: linux-i2c@vger.kernel.org
base-commit: cfaaa7d010d1fc58f9717fcc8591201e741d2d49
--
2.47.0.338.g60cca15819-goog
next reply other threads:[~2024-11-15 4:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 4:43 Brendan Higgins [this message]
2024-11-15 9:06 ` [RFC v1] MAINTAINERS: transfer i2c-aspeed maintainership from Brendan to Ryan Wolfram Sang
2024-11-15 15:24 ` Brendan Higgins
2024-11-18 0:25 ` Ryan Chen
2024-11-19 13:35 ` Andi Shyti
2024-11-19 23:51 ` Ryan Chen
2024-11-20 6:54 ` Andi Shyti
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=20241115044303.50877-1-brendanhiggins@google.com \
--to=brendanhiggins@google.com \
--cc=BMC-SW@aspeedtech.com \
--cc=andi.shyti@kernel.org \
--cc=andrew@codeconstruct.com.au \
--cc=benh@kernel.crashing.org \
--cc=brendan.higgins@linux.dev \
--cc=joel@jms.id.au \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=openbmc@lists.ozlabs.org \
--cc=ryan_chen@aspeedtech.com \
--cc=tommy_huang@aspeedtech.com \
--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