From: Chengming Zhou <chengming.zhou@linux.dev>
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-kernel@vger.kernel.org, vbabka@suse.cz,
roman.gushchin@linux.dev, Xiongwei.Song@windriver.com,
Chengming Zhou <zhouchengming@bytedance.com>
Subject: Re: [PATCH] freevxfs: remove SLAB_MEM_SPREAD flag usage
Date: Mon, 26 Feb 2024 18:24:32 +0800 [thread overview]
Message-ID: <e5709d61-18cf-4c6e-89b0-9615296c645a@linux.dev> (raw)
In-Reply-To: <ZdxiqJZY2qSRVvEU@infradead.org>
On 2024/2/26 18:06, Christoph Hellwig wrote:
> Please just do a scripted removal after next -rc1 instead of spamming
> everyone..
>
Do you mean put all diffs into a single patch, send it to all people?
That is also a choice if it's preferable. Should it will go through
the slab tree then?
Thanks.
next prev parent reply other threads:[~2024-02-26 10:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:48 [PATCH] freevxfs: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-26 10:06 ` Christoph Hellwig
2024-02-26 10:24 ` Chengming Zhou [this message]
2024-02-26 10:35 ` Vlastimil Babka
2024-02-26 10:49 ` Christoph Hellwig
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=e5709d61-18cf-4c6e-89b0-9615296c645a@linux.dev \
--to=chengming.zhou@linux.dev \
--cc=Xiongwei.Song@windriver.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@suse.cz \
--cc=zhouchengming@bytedance.com \
/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.