From: Trond Myklebust <trondmy@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-nfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [GIT PULL] Please pull another NFS client change for 6.2
Date: Fri, 17 Feb 2023 09:16:29 -0500 [thread overview]
Message-ID: <c2181ba919c59ffde5c9b9fc615608f92a146413.camel@kernel.org> (raw)
Hi Linus,
The following changes since commit ec35307e18ba8174e2a3f701956059f6a36f22fb:
Merge tag 'drm-fixes-2023-02-17' of git://anongit.freedesktop.org/drm/drm (2023-02-16 20:23:32 -0800)
are available in the Git repository at:
git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-6.2-3
for you to fetch changes up to 896e090eefedeb8a715ea19938a2791c32679cc9:
Revert "NFSv4.2: Change the default KConfig value for READ_PLUS" (2023-02-17 09:07:19 -0500)
Unfortunately, we found another bug in the NFSv4.2 READ_PLUS code.
Since it has not been possible to fix the bug in time for the 6.2
release, let's just revert the Kconfig change that enables it.
Thanks,
Trond
----------------------------------------------------------------
NFS client fixes for Linux 6.2
Bugfix:
- Revert "NFSv4.2: Change the default KConfig value for READ_PLUS"
----------------------------------------------------------------
Anna Schumaker (1):
Revert "NFSv4.2: Change the default KConfig value for READ_PLUS"
fs/nfs/Kconfig | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
--
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com
next reply other threads:[~2023-02-17 14:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-17 14:16 Trond Myklebust [this message]
2023-02-17 23:00 ` [GIT PULL] Please pull another NFS client change for 6.2 pr-tracker-bot
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=c2181ba919c59ffde5c9b9fc615608f92a146413.camel@kernel.org \
--to=trondmy@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=torvalds@linux-foundation.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