From: David Hildenbrand <david@redhat.com>
To: xu.xin16@zte.com.cn, lorenzo.stoakes@oracle.com
Cc: akpm@linux-foundation.org, chengming.zhou@linux.dev,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
yang.yang29@zte.com.cn, jiang.xuexin@zte.com.cn,
Liu.Jianjun3@zte.com.cn
Subject: Re: 答复: [RFC PATCH] MAINTAINERS: add mm ksm section
Date: Wed, 14 May 2025 10:14:10 +0200 [thread overview]
Message-ID: <a46874fc-d3bb-4cc7-871d-fd9791eb2e52@redhat.com> (raw)
In-Reply-To: <202505140950573489NhOV97K3BT0-xew40vNy@zte.com.cn>
On 14.05.25 03:50, xu.xin16@zte.com.cn wrote:
>>> I guess my point is, as a submitter you expect that people that are listed
>>> under R: that you are supposed to CC would actually ... review? :D
>>>
>>
>> Yeah of course, kinda makes sense right?
>>
>>> In that case, I would prefer to have actual reviewers there. If there are
>>> none, then there should be none listed.
>>>
>>> Of course, If Xu and Chengming do *want* to actively review KSM code
>>> changes, I would be more than happy to list them.
>>
>> Sure, so I think best thing is to ask:
>>
>> Xu, Chengming - do you WANT to be reviewers here? :) if not, happy to drop.
>
>
> Sure, I am more than willing to take on the role of reviewer for the KSM module.
> I am pleasured to dedicating my time to reviewing new patches about KSM on the
> mailing list. Thank you for the invitation.
Thanks to both of you, happy to hear that!
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2025-05-14 8:14 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-13 16:17 [RFC PATCH] MAINTAINERS: add mm ksm section Lorenzo Stoakes
2025-05-13 16:52 ` David Hildenbrand
2025-05-13 18:17 ` Lorenzo Stoakes
2025-05-13 19:05 ` David Hildenbrand
2025-05-13 19:09 ` Lorenzo Stoakes
2025-05-14 1:50 ` 答复: " xu.xin16
2025-05-14 8:14 ` David Hildenbrand [this message]
2025-05-14 2:31 ` Chengming Zhou
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=a46874fc-d3bb-4cc7-871d-fd9791eb2e52@redhat.com \
--to=david@redhat.com \
--cc=Liu.Jianjun3@zte.com.cn \
--cc=akpm@linux-foundation.org \
--cc=chengming.zhou@linux.dev \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
/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;
as well as URLs for NNTP newsgroup(s).