From: Jens Axboe <axboe@kernel.dk>
To: chengming.zhou@linux.dev
Cc: linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, vbabka@suse.cz, roman.gushchin@linux.dev,
Xiongwei.Song@windriver.com,
Chengming Zhou <zhouchengming@bytedance.com>
Subject: Re: [PATCH] bdev: remove SLAB_MEM_SPREAD flag usage
Date: Sat, 24 Feb 2024 13:16:39 -0700 [thread overview]
Message-ID: <170880579918.88310.13620256646819841520.b4-ty@kernel.dk> (raw)
In-Reply-To: <20240224134646.829105-1-chengming.zhou@linux.dev>
On Sat, 24 Feb 2024 13:46:46 +0000, chengming.zhou@linux.dev wrote:
> The SLAB_MEM_SPREAD flag is already a no-op as of 6.8-rc1, remove
> its usage so we can delete it from slab. No functional change.
>
>
Applied, thanks!
[1/1] bdev: remove SLAB_MEM_SPREAD flag usage
commit: 82c6515d8a970f471eeb8a5ceeaa04c3e5e1b45c
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2024-02-24 20:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:46 chengming.zhou
2024-02-24 20:16 ` Jens Axboe [this message]
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=170880579918.88310.13620256646819841520.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=Xiongwei.Song@windriver.com \
--cc=chengming.zhou@linux.dev \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox