From: Harry Yoo <harry@kernel.org>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: Mark Brown <broonie@kernel.org>, Vlastimil Babka <vbabka@suse.cz>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Puranjay Mohan <puranjay@kernel.org>,
Vlastimil Babka <vbabka@kernel.org>
Subject: Re: linux-next: manual merge of the slab tree with the rcu tree
Date: Sat, 1 Aug 2026 12:41:26 +0000 [thread overview]
Message-ID: <am3pO11Yshf_bgp-@dev> (raw)
In-Reply-To: <cdc6cf4f-57b2-475d-b9d3-23c4693ed871@paulmck-laptop>
On Thu, Jul 30, 2026 at 10:31:53AM -0700, Paul E. McKenney wrote:
> On Thu, Jul 30, 2026 at 03:38:48PM +0100, Mark Brown wrote:
> > Hi all,
> >
> > Today's linux-next merge of the slab tree got a conflict in:
> >
> > mm/slab_common.c
> >
> > between commit:
> >
> > 736084507faa3 ("rcu: Rename struct rcu_gp_oldstate to rcu_gp_seq")
> >
> > from the rcu tree and commit:
> >
> > bdd0cc9f0ffc3 ("mm/slab: introduce struct kvfree_rcu_head for kvfree_rcu batching")
> >
> > from the slab tree.
> >
> > I fixed it up (see below) and can carry the fix as necessary. This
> > is now fixed as far as linux-next is concerned, but any non trivial
> > conflicts should be mentioned to your upstream maintainer when your tree
> > is submitted for merging. You may also want to consider cooperating
> > with the maintainer of the conflicting tree to minimise any particularly
> > complex conflicts.
>
> This resolution looks good to me, thank you!
>
> Thanx, Paul
>
Looks good to me too, thanks!
--
Cheers,
Harry / Hyeonggon
next prev parent reply other threads:[~2026-08-01 12:41 UTC|newest]
Thread overview: 20+ 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 [this message]
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)
2026-08-04 8:26 ` Alice Ryhl
2026-08-04 8:44 ` 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=am3pO11Yshf_bgp-@dev \
--to=harry@kernel.org \
--cc=broonie@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=puranjay@kernel.org \
--cc=vbabka@kernel.org \
--cc=vbabka@suse.cz \
/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.