From: Chuck Lever <chuck.lever@oracle.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Bruce Fields <bfields@fieldses.org>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] nfsd changes for 5.11-rc
Date: Mon, 11 Jan 2021 09:40:40 -0500 [thread overview]
Message-ID: <BEF46BF0-8B84-468C-B88C-33202C786E7E@oracle.com> (raw)
Hi Linus-
The following changes since commit 5ee863bec794f30bdf7fdf57ce0d9f579b0d1aa3:
Merge branch 'parisc-5.11-1' of git://git.kernel.org/pub/scm/linux/kernel/git/deller/parisc-linux (2020-12-16 12:10:40 -0800)
are available in the Git repository at:
git://git.linux-nfs.org/projects/cel/cel-2.6.git 7b723008f9c95624c848fad661c01b06e47b20da
for you to fetch changes up to 7b723008f9c95624c848fad661c01b06e47b20da:
NFSD: Restore NFSv4 decoding's SAVEMEM functionality (2020-12-18 12:28:58 -0500)
----------------------------------------------------------------
Chuck Lever (3):
NFSD: Fix sparse warning in nfssvc.c
SUNRPC: Handle TCP socket sends with kernel_sendpage() again
NFSD: Restore NFSv4 decoding's SAVEMEM functionality
Trond Myklebust (2):
nfsd: Fixes for nfsd4_encode_read_plus_data()
nfsd: Don't set eof on a truncated READ_PLUS
fs/nfsd/nfs4proc.c | 5 +++++
fs/nfsd/nfs4xdr.c | 56 ++++++++++++++++++++++++++++++++++++--------------------
fs/nfsd/nfssvc.c | 6 ------
fs/nfsd/xdr4.h | 1 -
net/sunrpc/svcsock.c | 86 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++-
5 files changed, 126 insertions(+), 28 deletions(-)
--
Chuck Lever
next reply other threads:[~2021-01-11 14:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-11 14:40 Chuck Lever [this message]
2021-01-11 19:36 ` [GIT PULL] nfsd changes for 5.11-rc Linus Torvalds
2021-01-11 19:39 ` Chuck Lever
2021-01-11 20:14 ` 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=BEF46BF0-8B84-468C-B88C-33202C786E7E@oracle.com \
--to=chuck.lever@oracle.com \
--cc=bfields@fieldses.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.