From: Chengming Zhou <chengming.zhou@linux.dev>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Vlastimil Babka <vbabka@suse.cz>
Cc: David Rientjes <rientjes@google.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
patches@lists.linux.dev,
Roman Gushchin <roman.gushchin@linux.dev>,
Hyeonggon Yoo <42.hyeyoo@gmail.com>,
Xiongwei Song <xiongwei.song@windriver.com>
Subject: Re: [GIT PULL] slab updates for 6.9
Date: Wed, 13 Mar 2024 13:10:41 +0800 [thread overview]
Message-ID: <15e3cf4e-f8d3-4706-b667-2575659b5552@linux.dev> (raw)
In-Reply-To: <CAHk-=wiFUvms3x7BC1R_4-t80K3O_XTOW3BKp6nPL_FkFSPzzQ@mail.gmail.com>
On 2024/3/13 11:54, Linus Torvalds wrote:
> On Tue, 12 Mar 2024 at 02:55, Vlastimil Babka <vbabka@suse.cz> wrote:
>>
>> Also deprecate SLAB_MEM_SPREAD which was only
>> used by SLAB, so it's a no-op since SLAB removal. Assign it an explicit zero
>> value. The removals of the flag usage are handled independently in the
>> respective subsystems, with a final removal of any leftover usage planned
>> for the next release.
>
> I already had the patch ready to go:
>
> https://lore.kernel.org/all/CAHk-=wji0u+OOtmAOD-5JV3SXcRJF___k_+8XNKmak0yd5vW1Q@mail.gmail.com/
>
> so I just did a "git stash apply" and got rid of the final stragglers.
> No need to have various random maintainers have to worry about a flag
> that hasn't had any meaning since 6.7, and very little before that
> either.
Great! It's better. Thanks for doing this.
next prev parent reply other threads:[~2024-03-13 5:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-12 9:55 Vlastimil Babka
2024-03-13 3:54 ` Linus Torvalds
2024-03-13 5:10 ` Chengming Zhou [this message]
2024-03-13 9:28 ` Vlastimil Babka
2024-03-13 4:11 ` pr-tracker-bot
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=15e3cf4e-f8d3-4706-b667-2575659b5552@linux.dev \
--to=chengming.zhou@linux.dev \
--cc=42.hyeyoo@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=patches@lists.linux.dev \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=torvalds@linux-foundation.org \
--cc=vbabka@suse.cz \
--cc=xiongwei.song@windriver.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