From: "Thomas Weißschuh" <thomas@t-8ch.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Shuah Khan <skhan@linuxfoundation.org>, Willy Tarreau <w@1wt.eu>,
"Paul E. McKenney" <paulmck@kernel.org>,
Christian Brauner <brauner@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 nolibc tree
Date: Thu, 17 Aug 2023 18:30:54 +0200 [thread overview]
Message-ID: <e0af8d82-e099-49fa-9fbd-6f6bb63b7706@t-8ch.de> (raw)
In-Reply-To: <20230817133811.0a73c624@canb.auug.org.au>
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.
next prev parent reply other threads:[~2023-08-17 16:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-17 3:38 Stephen Rothwell
2023-08-17 16:30 ` Thomas Weißschuh [this message]
2023-08-17 18:27 ` Shuah Khan
2023-08-17 18:46 ` Paul E. McKenney
2023-08-17 19:39 ` Willy Tarreau
2023-08-17 20:41 ` Paul E. McKenney
2023-08-18 13:27 ` Christian Brauner
2023-08-18 13:59 ` Shuah Khan
2023-08-21 15:52 ` Shuah Khan
2023-08-21 16:07 ` Christian Brauner
2023-08-22 9:50 ` Willy Tarreau
2023-08-17 19:34 ` Thomas Weißschuh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e0af8d82-e099-49fa-9fbd-6f6bb63b7706@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=brauner@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=paulmck@kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=skhan@linuxfoundation.org \
--cc=w@1wt.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®