From: Calum Mackay <calum.mackay@oracle.com>
To: Linux NFS Mailing List <linux-nfs@vger.kernel.org>
Cc: Calum Mackay <calum.mackay@oracle.com>,
Jeff Layton <jlayton@kernel.org>, Dai Ngo <dai.ngo@oracle.com>,
Frank Filz <ffilzlnx@mindspring.com>,
Frank Filz <ffilz@redhat.com>
Subject: pynfs update
Date: Fri, 13 Oct 2023 21:30:09 +0100 [thread overview]
Message-ID: <df6491a1-0e22-482e-9c99-a30a772cfe9d@oracle.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 583 bytes --]
I've belatedly applied five of Jeff's patches from March (thank you) to
the pynfs tree, at:
http://git.linux-nfs.org/?p=cdmackay/pynfs.git;a=summary
Jeff Layton (5):
nfs4.0: add a retry loop on NFS4ERR_DELAY to compound function
examples: add a new example localhost_helper.sh script
nfs4.0/testserver.py: don't return an error when tests fail
testserver.py: add a new (special) "everything" flag
LOCK24: fix the lock_seqid in second lock request
I've get on with the rest of the pynfs backlog next week.
cheers,
calum.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
reply other threads:[~2023-10-13 20:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=df6491a1-0e22-482e-9c99-a30a772cfe9d@oracle.com \
--to=calum.mackay@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=ffilz@redhat.com \
--cc=ffilzlnx@mindspring.com \
--cc=jlayton@kernel.org \
--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