Linux-Next discussions
 help / color / mirror / Atom feed
From: "Vlastimil Babka (SUSE)" <vbabka@kernel.org>
To: Harry Yoo <harry@kernel.org>, Nathan Chancellor <nathan@kernel.org>
Cc: Alice Ryhl <aliceryhl@google.com>, Boqun Feng <boqun@kernel.org>,
	Miguel Ojeda <ojeda@kernel.org>,
	broonie@kernel.org, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, paulmck@kernel.org,
	puranjay@kernel.org,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Bert Karwatzki <spasswolf@web.de>
Subject: Re: linux-next: manual merge of the slab tree with the rcu tree
Date: Mon, 3 Aug 2026 15:33:55 +0200	[thread overview]
Message-ID: <a68ad6a2-f14d-4ee8-bdcc-16ea361a4428@kernel.org> (raw)
In-Reply-To: <anBBhmBSwLgcLjht@dev>

On 8/3/26 09:23, Harry Yoo wrote:
> On Fri, Jul 31, 2026 at 03:01:37PM -0700, Nathan Chancellor wrote:
>> On Fri, Jul 31, 2026 at 11:14:42PM +0200, Alice Ryhl wrote:
>> > I like Nathan's fix as well.
> 
> I don't really have a strong preference  this, and it would be
> appropriate to fix this in a way Rust folks would prefer...

It should be also possible to apply Miguel's fix immediately in the
char-misc tree, and then changing it to Nathan's fix as a followup clean-up
after both trees are mainline?

>> > Not sure if it needs to be done in the merge commit, or if we can
>> > apply it as a patch to char-misc despite the unknown CFG_*?
>> 
>> It would need to be applied at the merge of the two trees because
>> CONFIG_KVFREE_RCU_BATCHED was introduced back in 6.15 in commit
>> c9f8f1242a4c ("slab: don't batch kvfree_rcu() with SLUB_TINY").
> 
> What do we do when it needs to be fixed in the merge commit,
> mention this in the pull request email?
> 


  parent reply	other threads:[~2026-08-03 13:34 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-30 14:38 linux-next: manual merge of the slab tree with the rcu tree Mark Brown
2026-07-30 17:31 ` Paul E. McKenney
2026-08-01 12:41   ` Harry Yoo
2026-07-31  7:56 ` Miguel Ojeda
2026-07-31  9:59   ` Vlastimil Babka (SUSE)
2026-07-31 12:54     ` Vlastimil Babka (SUSE)
2026-07-31 20:07   ` Boqun Feng
2026-07-31 20:51     ` Miguel Ojeda
2026-07-31 21:14     ` Alice Ryhl
2026-07-31 22:01       ` Nathan Chancellor
2026-08-03  7:23         ` Harry Yoo
2026-08-03  8:07           ` Miguel Ojeda
2026-08-03 11:17             ` Harry Yoo
2026-08-03 12:21               ` Miguel Ojeda
2026-08-03 13:33           ` Vlastimil Babka (SUSE) [this message]
2026-08-04  8:26         ` Alice Ryhl
2026-08-04  8:44           ` Vlastimil Babka (SUSE)
2026-08-04 10:01             ` Miguel Ojeda
2026-08-04 10:39               ` Vlastimil Babka (SUSE)
  -- strict thread matches above, loose matches on Subject: below --
2025-02-12  4:09 Stephen Rothwell
2025-02-12  5:34 ` Boqun Feng
2024-08-12  2:47 Stephen Rothwell

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=a68ad6a2-f14d-4ee8-bdcc-16ea361a4428@kernel.org \
    --to=vbabka@kernel.org \
    --cc=aliceryhl@google.com \
    --cc=boqun@kernel.org \
    --cc=broonie@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=harry@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=nathan@kernel.org \
    --cc=ojeda@kernel.org \
    --cc=paulmck@kernel.org \
    --cc=puranjay@kernel.org \
    --cc=spasswolf@web.de \
    /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