linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Ye Liu <ye.liu@linux.dev>
To: Markus Elfring <Markus.Elfring@web.de>, Ye Liu <liuye@kylinos.cn>,
	linux-mm@kvack.org, Matthew Wilcox <willy@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Anshuman Khandual <anshuman.khandual@arm.com>,
	Sidhartha Kumar <sidhartha.kumar@oracle.com>
Subject: Re: [v4] mm/page_alloc: Consolidate unlikely handling in page_expected_state
Date: Mon, 31 Mar 2025 20:51:28 +0800	[thread overview]
Message-ID: <9ee54186-b56c-4876-a36f-1e4fb1835d09@linux.dev> (raw)
In-Reply-To: <05ebb2eb-5f66-4613-a39e-40194c96341f@web.de>


在 2025/3/31 20:21, Markus Elfring 写道:
>> Regarding the reviewer shortage, I’d be happy to help by reviewing
>> other patches as well. Could you please share the process for becoming
>> a reviewer?
> Under which circumstances would you dare to comment information from
> other contributors?
>
> How will your development interests evolve further?
>
>
>>             What are the requirements or steps to get involved?
> You can try to improve communication skills as needed.

I don’t see how I’ve offended anyone.
         -- I was simply asking about the process to become a reviewer.
What exactly is the issue with that?
How did you interpret my message to warrant such a response?

Thanks,
Ye Liu



  reply	other threads:[~2025-03-31 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  1:47 [PATCH v4] " Ye Liu
2025-03-28  9:44 ` Markus Elfring
2025-03-28 14:29 ` Matthew Wilcox
2025-03-31 12:08   ` Ye Liu
2025-03-31 12:21     ` [v4] " Markus Elfring
2025-03-31 12:51       ` Ye Liu [this message]
2025-03-31 13:15         ` Markus Elfring
2025-03-31 15:53         ` Matthew Wilcox
2025-04-02  2:51           ` Ye Liu
2025-03-31 15:59     ` [PATCH v4] " Matthew Wilcox
2025-04-02  2:49       ` Ye Liu
2025-04-03  3:55         ` Vishal Moola (Oracle)
2025-04-03  5:58           ` Ye Liu

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=9ee54186-b56c-4876-a36f-1e4fb1835d09@linux.dev \
    --to=ye.liu@linux.dev \
    --cc=Markus.Elfring@web.de \
    --cc=akpm@linux-foundation.org \
    --cc=anshuman.khandual@arm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=liuye@kylinos.cn \
    --cc=sidhartha.kumar@oracle.com \
    --cc=willy@infradead.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