Received-SPF: pass (google.com: domain of linux-kernel+bounces-84332-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Date: Tue, 27 Feb 2024 17:26:56 -0800
From: "Paul E. McKenney" <paulmck@kernel.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>, 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>,
	x86@kernel.org
Subject: Re: linux-next: duplicate patch in the rcu tree
Message-ID: <f95f6787-ed54-4b4d-afbc-30ed25bbf31f@paulmck-laptop>
Reply-To: paulmck@kernel.org
References: <20240228120610.0fdd20af@canb.auug.org.au>
 <87jzmp8k1a.ffs@tglx>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <87jzmp8k1a.ffs@tglx>

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