From: Stephen Rothwell <sfr@rothwell.id.au>
To: Andrew Morton <akpm@linux-foundation.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>,
Peter Zijlstra <peterz@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: duplicate patch in the tip tree
Date: Tue, 29 Oct 2024 17:05:33 +1100 [thread overview]
Message-ID: <20241029170533.5592ab42@oak> (raw)
In-Reply-To: <20241028213040.e5d72b2f56971ceb5c80395b@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 871 bytes --]
Hi Andrew,
On Mon, 28 Oct 2024 21:30:40 -0700 Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 29 Oct 2024 13:34:07 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> > The following commit is also in the mm-hotfixes tree as a different commit
> > (but the same patch):
> >
> > 9c70b2a33cd2 ("sched/numa: Fix the potential null pointer dereference in task_numa_work()")
> >
> > This is commit
> >
> > 82c4d6b6dace ("sched/numa: fix the potential null pointer dereference in task_numa_work()")
> >
> > in the mm-hotfixes-unstable branch of the mm-hotfixes tree.
>
> Thanks, but... What tip branch is it in? Matters because: is that
> branch destined for 6.12.x?
Its in the sched/urgent branch, so probably destined for Linus fairly
soon. But the tip guys would know better than I.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-10-29 6:13 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 2:34 linux-next: duplicate patch in the tip tree Stephen Rothwell
2024-10-29 4:30 ` Andrew Morton
2024-10-29 6:05 ` Stephen Rothwell [this message]
2024-10-29 7:52 ` Thomas Gleixner
2024-10-29 11:08 ` Peter Zijlstra
-- strict thread matches above, loose matches on Subject: below --
2025-09-12 3:09 Stephen Rothwell
2025-09-16 8:37 ` Lee Jones
2025-07-08 6:00 Stephen Rothwell
2025-07-08 6:48 ` Andrew Morton
2025-07-09 9:17 ` Borislav Petkov
2025-07-09 19:12 ` Andrew Morton
2025-07-09 19:43 ` Borislav Petkov
2025-05-12 5:04 Stephen Rothwell
2025-05-07 3:22 Stephen Rothwell
2025-05-07 7:55 ` Thomas Gleixner
2025-05-07 17:44 ` Ingo Molnar
2025-04-16 3:21 Stephen Rothwell
2025-04-16 14:38 ` Gregory CLEMENT
2025-02-27 3:44 Stephen Rothwell
2025-02-27 3:48 ` Stephen Rothwell
2025-02-27 4:40 ` Andrew Morton
2025-01-15 5:33 Stephen Rothwell
2024-09-11 5:24 Stephen Rothwell
2024-03-11 21:28 Stephen Rothwell
2023-10-04 2:33 Stephen Rothwell
2023-10-04 13:32 ` Jonathan Corbet
2023-10-04 15:41 ` Ingo Molnar
2023-06-02 3:04 Stephen Rothwell
2023-06-02 17:05 ` Andrew Morton
2023-01-13 1:40 Stephen Rothwell
2023-01-13 16:27 ` Jonathan Corbet
2023-01-13 21:51 ` 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=20241029170533.5592ab42@oak \
--to=sfr@rothwell.id.au \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tglx@linutronix.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;
as well as URLs for NNTP newsgroup(s).