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: very bad update of the nfsd tree
Date: Thu, 21 Nov 2024 10:12:01 +1100 [thread overview]
Message-ID: <20241121101201.0c5a7ee1@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 413 bytes --]
Hi all,
It looks like the nfsd tree
(git://git.kernel.org/pub/scm/linux/kernel/git/cel/linux branch
nfsd-next) is now based on v5.4.286 which is incompatible with being in
linux-next. Please reset your nfsd-next branch to something based on
Linus' tree. I will use the nfsd tree from yesterday (HEAD is
583772eec7b0 "nfsd: allow for up to 32 callback session slots").
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
reply other threads:[~2024-11-20 23:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20241121101201.0c5a7ee1@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=chuck.lever@oracle$(echo .)com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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