From: Jeff Layton <jlayton@kernel.org>
To: Tom Talpey <tom@talpey.com>,
Dan Shelton <dan.f.shelton@gmail.com>,
Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Subject: Re: Public NFSv4 handle?
Date: Fri, 09 Feb 2024 06:09:48 -0500 [thread overview]
Message-ID: <499f0666e84dfcaab26d96dac3437fec3afa88d8.camel@kernel.org> (raw)
In-Reply-To: <b14648b0-a2f7-451a-a56b-6bb626c4ffa8@talpey.com>
next prev parent reply other threads:[~2024-02-09 11:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-25 1:48 Public NFSv4 handle? Dan Shelton
2024-02-09 0:19 ` Dan Shelton
2024-02-09 2:37 ` Tom Talpey
2024-02-09 11:09 ` Jeff Layton [this message]
2024-02-09 14:52 ` Jeff Layton
2024-02-09 15:32 ` Jeff Layton
2024-02-13 20:28 ` Dan Shelton
2024-02-13 20:42 ` Jeff Layton
2024-02-13 20:58 ` Trond Myklebust
2024-02-14 6:12 ` Cedric Blancher
2024-02-15 17:25 ` Frank Filz
2024-02-13 21:16 ` Chuck Lever III
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=499f0666e84dfcaab26d96dac3437fec3afa88d8.camel@kernel.org \
--to=jlayton@kernel.org \
--cc=dan.f.shelton@gmail.com \
--cc=linux-nfs@vger.kernel.org \
--cc=tom@talpey.com \
/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;
as well as URLs for NNTP newsgroup(s).