From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: 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, 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
Subject: Re: [RFC v1] MAINTAINERS: transfer i2c-aspeed maintainership from Brendan to Ryan
Date: Fri, 15 Nov 2024 10:06:47 +0100 [thread overview]
Message-ID: <ZzcPJ9sweqxLZOGf@ninjato> (raw)
In-Reply-To: <20241115044303.50877-1-brendanhiggins@google.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Fri, Nov 15, 2024 at 04:43:03AM +0000, Brendan Higgins wrote:
> 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
Thanks for your work on this driver.
> 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?
I am fine, depends on Ryan as far as I am concerned.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Brendan Higgins <brendanhiggins@google.com>
Cc: BMC-SW@aspeedtech.com, ryan_chen@aspeedtech.com,
andi.shyti@kernel.org, linux-aspeed@lists.ozlabs.org,
openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org,
wsa@kernel.org, brendan.higgins@linux.dev,
linux-i2c@vger.kernel.org, tommy_huang@aspeedtech.com,
joel@jms.id.au
Subject: Re: [RFC v1] MAINTAINERS: transfer i2c-aspeed maintainership from Brendan to Ryan
Date: Fri, 15 Nov 2024 10:06:47 +0100 [thread overview]
Message-ID: <ZzcPJ9sweqxLZOGf@ninjato> (raw)
In-Reply-To: <20241115044303.50877-1-brendanhiggins@google.com>
[-- Attachment #1: Type: text/plain, Size: 962 bytes --]
On Fri, Nov 15, 2024 at 04:43:03AM +0000, Brendan Higgins wrote:
> 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
Thanks for your work on this driver.
> 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?
I am fine, depends on Ryan as far as I am concerned.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-11-15 9:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-15 4:43 [RFC v1] MAINTAINERS: transfer i2c-aspeed maintainership from Brendan to Ryan Brendan Higgins
2024-11-15 4:43 ` Brendan Higgins
2024-11-15 9:06 ` Wolfram Sang [this message]
2024-11-15 9:06 ` Wolfram Sang
2024-11-15 15:24 ` Brendan Higgins
2024-11-18 0:25 ` Ryan Chen
2024-11-18 0:25 ` Ryan Chen
2024-11-19 13:35 ` Andi Shyti
2024-11-19 13:35 ` Andi Shyti
2024-11-19 23:51 ` Ryan Chen
2024-11-19 23:51 ` Ryan Chen
2024-11-20 6:54 ` Andi Shyti
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=ZzcPJ9sweqxLZOGf@ninjato \
--to=wsa+renesas@sang-engineering.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=brendanhiggins@google.com \
--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 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.