All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Kleikamp <dave.kleikamp@oracle.com>
To: Christian Brauner <brauner@kernel.org>,
	shaggy@kernel.org, jack@suse.cz, jlayton@kernel.org,
	chuck.lever@oracle.com, zhouchengming@bytedance.com,
	chengming.zhou@linux.dev
Cc: amir73il@gmail.com, jfs-discussion@lists.sourceforge.net,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org, vbabka@suse.cz,
	roman.gushchin@linux.dev, Xiongwei.Song@windriver.com
Subject: Re: [PATCH] jfs: remove SLAB_MEM_SPREAD flag usage
Date: Tue, 27 Feb 2024 08:22:22 -0600	[thread overview]
Message-ID: <dc3fe8c5-e552-48c1-989a-1fbfd89d1109@oracle.com> (raw)
In-Reply-To: <20240227-erlischt-filmpreis-b637a1cd3693@brauner>

On 2/27/24 4:52AM, Christian Brauner wrote:
> On Sat, 24 Feb 2024 13:49:25 +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.
>>
>>
> 
> Updated commit message to point to slab removal.
Acked-by: Dave Kleikamp <dave.kleikamp@oracle.com>

> 
> ---
> 
> Applied to the vfs.misc branch of the vfs/vfs.git tree.
> Patches in the vfs.misc branch should appear in linux-next soon.
> 
> Please report any outstanding bugs that were missed during review in a
> new review to the original patch series allowing us to drop it.
> 
> It's encouraged to provide Acked-bys and Reviewed-bys even though the
> patch has now been applied. If possible patch trailers will be updated.
> 
> Note that commit hashes shown below are subject to change due to rebase,
> trailer updates or similar. If in doubt, please check the listed branch.
> 
> tree:   https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
> branch: vfs.misc
> 
> [1/1] jfs: remove SLAB_MEM_SPREAD flag usage
>        https://git.kernel.org/vfs/vfs/c/6259e5e07b76


      reply	other threads:[~2024-02-27 14:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-24 13:49 [PATCH] jfs: remove SLAB_MEM_SPREAD flag usage chengming.zhou
2024-02-27 10:52 ` Christian Brauner
2024-02-27 14:22   ` Dave Kleikamp [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=dc3fe8c5-e552-48c1-989a-1fbfd89d1109@oracle.com \
    --to=dave.kleikamp@oracle.com \
    --cc=Xiongwei.Song@windriver.com \
    --cc=amir73il@gmail.com \
    --cc=brauner@kernel.org \
    --cc=chengming.zhou@linux.dev \
    --cc=chuck.lever@oracle.com \
    --cc=jack@suse.cz \
    --cc=jfs-discussion@lists.sourceforge.net \
    --cc=jlayton@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=roman.gushchin@linux.dev \
    --cc=shaggy@kernel.org \
    --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.