All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trond Myklebust <trondmy@hammerspace.com>
To: "torvalds@linux-foundation.org" <torvalds@linux-foundation.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: [GIT PULL] Please pull NFS client bugfix for 4.20
Date: Sun, 4 Nov 2018 13:56:40 +0000	[thread overview]
Message-ID: <9d585276a55d788b98ba425910cd4a05a9e5cf99.camel@hammerspace.com> (raw)

Hi Linus,

The following changes since commit 86bbd7422ae6a33735df6846fd685e46686da714:

  NFS: change sign of nfs_fh length (2018-10-23 12:22:21 -0400)

are available in the Git repository at:

  git://git.linux-nfs.org/projects/trondmy/linux-nfs.git tags/nfs-for-4.20-2

for you to fetch changes up to d3787af289c85381cc048cb8c56b67260dbbc436:

  NFS: fix spelling mistake, EACCESS -> EACCES (2018-11-01 14:07:06 -0400)

Thanks,
  Trond

----------------------------------------------------------------
NFS client bugfixes for Linux 4.20

Highlights include:

Bugfixes:
- Fix build issues on architectures that don't provide 64-bit cmpxchg

Cleanups:
- Fix a spelling mistake

----------------------------------------------------------------
Colin Ian King (1):
      NFS: fix spelling mistake, EACCESS -> EACCES

Paul Burton (1):
      SUNRPC: Use atomic(64)_t for seq_send(64)

 fs/nfs/nfs4proc.c                   |  2 +-
 include/linux/sunrpc/gss_krb5.h     |  7 ++-----
 net/sunrpc/auth_gss/gss_krb5_mech.c | 16 ++++++++++------
 net/sunrpc/auth_gss/gss_krb5_seal.c | 28 ++--------------------------
 net/sunrpc/auth_gss/gss_krb5_wrap.c |  4 ++--
 5 files changed, 17 insertions(+), 40 deletions(-)
-- 
Trond Myklebust
Linux NFS client maintainer, Hammerspace
trond.myklebust@hammerspace.com



             reply	other threads:[~2018-11-04 13:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-04 13:56 Trond Myklebust [this message]
2018-11-04 16:21 ` [GIT PULL] Please pull NFS client bugfix for 4.20 Linus Torvalds

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=9d585276a55d788b98ba425910cd4a05a9e5cf99.camel@hammerspace.com \
    --to=trondmy@hammerspace.com \
    --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 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.