From: Andrew Morton <akpm@linux-foundation•org>
To: Peter Zijlstra <peterz@infradead•org>
Cc: Stephen Rothwell <sfr@canb•auug.org.au>,
Thomas Gleixner <tglx@linutronix•de>,
Ingo Molnar <mingo@redhat•com>, "H. Peter Anvin" <hpa@zytor•com>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>,
Linux Next Mailing List <linux-next@vger•kernel.org>,
surenb@google•com
Subject: Re: linux-next: duplicate patches in the tip tree
Date: Mon, 9 Dec 2024 11:45:24 -0800 [thread overview]
Message-ID: <20241209114524.a150aba86198e6f0fc9afcbc@linux-foundation.org> (raw)
In-Reply-To: <20241209110842.GM21636@noisy.programming.kicks-ass.net>
On Mon, 9 Dec 2024 12:08:42 +0100 Peter Zijlstra <peterz@infradead•org> wrote:
> On Mon, Dec 09, 2024 at 01:29:41PM +1100, Stephen Rothwell wrote:
> > Hi all,
> >
> > The following commits are also in the mm tree as different commits
> > (but the same patches):
> >
> > 96450ead1652 ("seqlock: add raw_seqcount_try_begin")
> > eb449bd96954 ("mm: convert mm_lock_seq to a proper seqcount")
> >
> > These are commits
> >
> > 46dbe8ab1205 ("seqlock: add raw_seqcount_try_begin")
> > 5f0d64389e1f ("mm: convert mm_lock_seq to a proper seqcount")
> >
> > from the mm-unstable branch of the mm tree. The latter ones are already
> > causing conflicts.
>
> Why is this in -mm ?
Because
https://lore.kernel.org/all/20241206225204.4008261-1-surenb@google.com/T/#u
needs it.
> I agreed with Suren I'd take them through
> tip/perf/core to go along with Andrii's uprobe patch that relies on
> them.
next prev parent reply other threads:[~2024-12-09 19:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 2:29 linux-next: duplicate patches in the tip tree Stephen Rothwell
2024-12-09 11:08 ` Peter Zijlstra
2024-12-09 19:45 ` Andrew Morton [this message]
2024-12-09 20:21 ` Suren Baghdasaryan
2024-12-09 22:53 ` Thomas Gleixner
-- strict thread matches above, loose matches on Subject: below --
2025-03-20 9:46 Stephen Rothwell
2025-03-20 11:13 ` Mark Brown
2025-03-11 4:08 Stephen Rothwell
2025-03-11 9:02 ` Andrew Morton
2025-03-11 11:43 ` Stephen Rothwell
2025-03-11 12:56 ` Thomas Gleixner
2025-03-25 21:47 ` Stephen Rothwell
2024-11-18 21:02 Stephen Rothwell
2024-03-03 22:21 Stephen Rothwell
2024-03-04 9:21 ` Ingo Molnar
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=20241209114524.a150aba86198e6f0fc9afcbc@linux-foundation.org \
--to=akpm@linux-foundation$(echo .)org \
--cc=hpa@zytor$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=mingo@redhat$(echo .)com \
--cc=peterz@infradead$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
--cc=surenb@google$(echo .)com \
--cc=tglx@linutronix$(echo .)de \
/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