Re: linux-next: duplicate patch in the nolibc tree

["Thomas Weißschuh" <thomas@t-8ch.de>]

On 2023-08-17 12:27:46-0600, Shuah Khan wrote:
> On 8/17/23 10:30, Thomas Weißschuh wrote:
> > On 2023-08-17 13:38:11+1000, Stephen Rothwell wrote:
> > > The following commit is also in the vfs-brauner tree as a different commit
> > > (but the same patch):
> > > 
> > >    ba859b2e419c ("selftests/nolibc: drop test chmod_net")
> > > 
> > > This is commit
> > > 
> > >    49319832de90 ("selftests/nolibc: drop test chmod_net")
> > > 
> > > in the vfs-brauner tree.
> > 
> > I think we can drop the patch from the nolibc tree.
> > The patch is only really necessary in combination with
> > commit 18e66ae67673 ("proc: use generic setattr() for /proc/$PID/net")
> > which already is and should stay in the vfs tree.
> 
> Thomas,
> 
> Do the rest of the nolibc patches build without this if we were
> to drop this patch? Dorpping requires rebase and please see below.

Yes, this patch is completely independent.
It only interacts with the mentioned commit in the vfs tree.

> [..]

Thomas