[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20241028213040.e5d72b2f56971ceb5c80395b@linux-foundation.org>
Date: Mon, 28 Oct 2024 21:30:40 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, Peter Zijlstra <peterz@...radead.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Linux Next
Mailing List <linux-next@...r.kernel.org>
Subject: Re: linux-next: duplicate patch in the tip tree
On Tue, 29 Oct 2024 13:34:07 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi all,
>
> 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?
Powered by blists - more mailing lists