[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-next
Subject:    Re: linux-next: duplicate patch in the rcu tree
From:       "Paul E. McKenney" <paulmck () kernel ! org>
Date:       2024-02-28 1:26:56
Message-ID: f95f6787-ed54-4b4d-afbc-30ed25bbf31f () paulmck-laptop
[Download RAW message or body]

On Wed, Feb 28, 2024 at 02:17:05AM +0100, Thomas Gleixner wrote:
> On Wed, Feb 28 2024 at 12:06, Stephen Rothwell wrote:
> > The following commit is also in the tip tree as a different commit
> > (but the same patch):
> >
> >   020eee167cca ("x86/nmi: Fix "in NMI handler" check")
> >
> > This is commit
> >
> >   d54e56f31a34 ("x86/nmi: Fix the inverse "in NMI handler" check")
> >
> > in the tip tree.
> 
> And why the heck is the RCU tree carrying x86 specific stuff which has
> absolutely nothing to do with RCU?
> 
> Just because, right?

So I could test it.

In the future, I will keep such commits out of the portion of -rcu that
is sent to -next.  Apologies for slipping up this time.

							Thanx, Paul

[prev in list] [next in list] [prev in thread] [next in thread]