Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 11 May 2023 09:52:47 -0700
From:   "Paul E. McKenney" <paulmck@kernel.org>
To:     Stephen Rothwell <sfr@canb.auug.org.au>
Cc:     Shuah Khan <shuah@kernel.org>,
        Shuah Khan <skhan@linuxfoundation.org>,
        Mark Brown <broonie@kernel.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 rcu tree
Message-ID: <59c2fd36-6920-47d8-a79c-9ff3fcf7c7ae@paulmck-laptop>
Reply-To: paulmck@kernel.org
References: <20230511090010.2916e9d7@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20230511090010.2916e9d7@canb.auug.org.au>
Precedence: bulk

On Thu, May 11, 2023 at 09:00:10AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> The following commit is also in the kselftest-fixes tree as a different
> commit (but the same patch):
> 
>   6d9ed63d8bc3 ("tools/nolibc: Fix build of stdio.h due to header ordering")
> 
> This is commit
> 
>   d7eafa64a158 ("tools/nolibc: Fix build of stdio.h due to header ordering")
> 
> in the kselftest-fixes tree.

I can currently cleanly remove this commit from the rest of the nolibc
commits in -rcu.

However, I might need to re-introduce it in some way or another, for
example, if there are dependencies on it by future nolibc patches.
(I expect another batch in a few days.)

So how would you like to proceed?

							Thanx, Paul