From: Benjamin Coddington <bcodding@redhat.com>
To: linux-nfs@vger.kernel.org
Cc: chuck.lever@oracle.com
Subject: [PATCH 0/2] nfsidmap not setting key timeouts
Date: Mon, 3 Nov 2014 12:49:31 -0500 [thread overview]
Message-ID: <cover.1415036893.git.bcodding@redhat.com> (raw)
These should fix up nfsidmap being unable to set key timeouts.
Benjamin Coddington (2):
nfsidmap: set the correct DEFAULT_KEYRING string
nfsidmap: Correct a failure to set key timeout values
utils/nfsidmap/nfsidmap.c | 5 ++++-
1 files changed, 4 insertions(+), 1 deletions(-)
next reply other threads:[~2014-11-03 17:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-03 17:49 Benjamin Coddington [this message]
2014-11-03 17:49 ` [PATCH 1/2] nfsidmap: set the correct DEFAULT_KEYRING string Benjamin Coddington
2014-11-03 17:49 ` [PATCH 2/2] nfsidmap: Correct a failure to set key timeout values Benjamin Coddington
2014-11-03 20:43 ` [PATCH 0/2] nfsidmap not setting key timeouts Chuck Lever
2014-11-04 19:49 ` Steve Dickson
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=cover.1415036893.git.bcodding@redhat.com \
--to=bcodding@redhat.com \
--cc=chuck.lever@oracle.com \
--cc=linux-nfs@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