From: Ridong Chen <ridong.chen@linux.dev>
To: "Michal Koutný" <mkoutny@suse.com>, "Waiman Long" <longman@redhat.com>
Cc: Tejun Heo <tj@kernel.org>, Johannes Weiner <hannes@cmpxchg.org>,
cgroups@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] cgroup/cpuset: Remove Chen Ridong as a cpust reviewer for now
Date: Tue, 2 Jun 2026 16:13:43 +0800 [thread overview]
Message-ID: <69b82f73-e89a-4271-a494-3c4d5684b7ac@linux.dev> (raw)
In-Reply-To: <ah6LAfpMsdPLun2_@localhost.localdomain>
On 2026/6/2 15:51, Michal Koutný wrote:
> +Cc: ridong.chen@linux.dev
>
> (This looks like their new address.)
>
Hi all,
Thank you, Michal.
Apologies for the email issue. I'm currently changing my company, The
ridong.chen@linux.dev email is valid.
> On Mon, Jun 01, 2026 at 10:44:22PM -0400, Waiman Long <longman@redhat.com> wrote:
>> Chen Ridong has contributed quite a lot of fixes and cleanups to the
>> cpuset code. Unfortunately, his email address is now no longer valid. So
>> remove him as a cpuset reviewer until he shows up again or someone else
>> volunteers to take his place.
>>
>> Signed-off-by: Waiman Long <longman@redhat.com>
>> ---
>> MAINTAINERS | 1 -
>> 1 file changed, 1 deletion(-)
>>
>> diff --git a/MAINTAINERS b/MAINTAINERS
>> index 74c86cf9bc65..c7a7126ea406 100644
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -6526,7 +6526,6 @@ F: include/linux/blk-cgroup.h
>>
>> CONTROL GROUP - CPUSET
>> M: Waiman Long <longman@redhat.com>
>> -R: Chen Ridong <chenridong@huaweicloud.com>
>> L: cgroups@vger.kernel.org
>> S: Maintained
>> T: git git://git.kernel.org/pub/scm/linux/kernel/git/tj/cgroup.git
>> --
>> 2.54.0
>>
--
Best regards,
Ridong
next prev parent reply other threads:[~2026-06-02 8:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 2:44 [PATCH] cgroup/cpuset: Remove Chen Ridong as a cpust reviewer for now Waiman Long
2026-06-02 7:51 ` Michal Koutný
2026-06-02 8:13 ` Ridong Chen [this message]
2026-06-02 18:35 ` Waiman Long
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=69b82f73-e89a-4271-a494-3c4d5684b7ac@linux.dev \
--to=ridong.chen@linux.dev \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mkoutny@suse.com \
--cc=tj@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.