public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel•org
To: Chengming Zhou <chengming.zhou@linux•dev>
Cc: horms@kernel•org, davem@davemloft•net, edumazet@google•com,
	kuba@kernel•org, netdev@vger•kernel.org,
	zhouchengming@bytedance•com
Subject: Re: [PATCH v2] net: remove SLAB_MEM_SPREAD flag usage
Date: Thu, 29 Feb 2024 03:50:29 +0000	[thread overview]
Message-ID: <170917862963.28712.8604356549822328231.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240228030658.3512782-1-chengming.zhou@linux.dev>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel•org>:

On Wed, 28 Feb 2024 03:06:58 +0000 you 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.
> 
> [...]

Here is the summary with links:
  - [v2] net: remove SLAB_MEM_SPREAD flag usage
    https://git.kernel.org/netdev/net-next/c/d4f01c5e477a

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2024-02-29  3:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 13:49 [PATCH] net: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-26  8:55 ` Chengming Zhou
2024-02-27 17:09   ` Simon Horman
2024-02-28  3:06     ` [PATCH v2] " Chengming Zhou
2024-02-28 15:04       ` Simon Horman
2024-02-29  3:50       ` patchwork-bot+netdevbpf [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=170917862963.28712.8604356549822328231.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel$(echo .)org \
    --cc=chengming.zhou@linux$(echo .)dev \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=horms@kernel$(echo .)org \
    --cc=kuba@kernel$(echo .)org \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=zhouchengming@bytedance$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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