From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: duplicate patches in the nfsd tree
Date: Wed, 5 Apr 2023 08:25:39 +1000 [thread overview]
Message-ID: <20230405082539.3e8d1ab9@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 621 bytes --]
Hi all,
The following commits are also in Linus Torvalds' tree as different
commits (but the same patches):
a98c27281895 ("sunrpc: only free unix grouplist after RCU settles")
691a90426c2f ("NFS: Remove "select RPCSEC_GSS_KRB5")
64208e19495c ("NFSD: callback request does not use correct credential for AUTH_SYS")
these are commits
5085e41f9e83 ("sunrpc: only free unix grouplist after RCU settles")
8be8f170e838 ("NFS: Remove "select RPCSEC_GSS_KRB5")
7de82c2f36fb ("NFSD: callback request does not use correct credential for AUTH_SYS")
in Linus' tree.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2023-04-04 22:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-04 22:25 Stephen Rothwell [this message]
2023-04-05 0:38 ` Chuck Lever III
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=20230405082539.3e8d1ab9@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=chuck.lever@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
/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®