Subject: Re: linux-next: duplicate patch in the tip tree

From: Peter Zijlstra <[email-masked]>
Date: Tue, 29 Oct 2024 12:08:30 +0100

On Tue, Oct 29, 2024 at 05:05:33PM +1100, Stephen Rothwell wrote:
> Hi Andrew,
> 
> On Mon, 28 Oct 2024 21:30:40 -0700 Andrew Morton <[email-masked]> wrote:
> >
> > On Tue, 29 Oct 2024 13:34:07 +1100 Stephen Rothwell <[email-masked]> 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.

Yeah, tip/sched/urgent, which is supposed to go to Linus on Sunday
before he cuts the next -rc or so.