From: Simon Horman <horms@kernel.org>
To: Chengming Zhou <chengming.zhou@linux.dev>
Cc: chuck.lever@oracle.com, jlayton@kernel.org, neilb@suse.de,
kolga@netapp.com, linux-nfs@vger.kernel.org,
netdev@vger.kernel.org,
Chengming Zhou <zhouchengming@bytedance.com>
Subject: Re: [PATCH v3] sunrpc: remove SLAB_MEM_SPREAD flag usage
Date: Wed, 28 Feb 2024 15:06:46 +0000 [thread overview]
Message-ID: <20240228150646.GJ292522@kernel.org> (raw)
In-Reply-To: <20240228031234.3512969-1-chengming.zhou@linux.dev>
On Wed, Feb 28, 2024 at 03:12:34AM +0000, Chengming Zhou wrote:
> From: Chengming Zhou <zhouchengming@bytedance.com>
>
> The SLAB_MEM_SPREAD flag used to be implemented in SLAB, which was
> removed as of v6.8-rc1, so it became a dead flag since the commit
> 16a1d968358a ("mm/slab: remove mm/slab.c and slab_def.h"). And the
> series[1] went on to mark it obsolete to avoid confusion for users.
> Here we can just remove all its users, which has no functional change.
>
> [1] https://lore.kernel.org/all/20240223-slab-cleanup-flags-v2-1-02f1753e8303@suse.cz/
>
> Signed-off-by: Chengming Zhou <zhouchengming@bytedance.com>
> ---
> v3:
> - Improve the indentation, per Simon Horman.
>
> v2:
> - Update the patch description and include the related link to
> make it clearer that SLAB_MEM_SPREAD flag is now a no-op.
Thanks for the updates.
Reviewed-by: Simon Horman <horms@kernel.org>
In future please consider the following:
1. Don't post new revisions of a series more than once every 24h
2. Do post new revisions as new email threads
Link: https://docs.kernel.org/process/maintainer-netdev.html
prev parent reply other threads:[~2024-02-28 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-24 13:51 [PATCH] sunrpc: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-26 4:23 ` Chengming Zhou
2024-02-27 17:13 ` Simon Horman
2024-02-28 3:00 ` [PATCH v2] " Chengming Zhou
2024-02-28 3:12 ` [PATCH v3] " Chengming Zhou
2024-02-28 15:06 ` Simon Horman [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=20240228150646.GJ292522@kernel.org \
--to=horms@kernel.org \
--cc=chengming.zhou@linux.dev \
--cc=chuck.lever@oracle.com \
--cc=jlayton@kernel.org \
--cc=kolga@netapp.com \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=netdev@vger.kernel.org \
--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.