From: Petr Vorel <pvorel@suse.cz>
To: Jeff Layton <jlayton@kernel.org>
Cc: calum.mackay@oracle.com, bfields@fieldses.org,
ffilzlnx@mindspring.com, linux-nfs@vger.kernel.org,
Frank Filz <ffilz@redhat.com>
Subject: Re: [pynfs PATCH v2 5/5] LOCK24: fix the lock_seqid in second lock request
Date: Tue, 28 Mar 2023 15:23:07 +0200 [thread overview]
Message-ID: <20230328132307.GA780540@pevik> (raw)
In-Reply-To: <20230313112401.20488-6-jlayton@kernel.org>
Hi Jeff,
thanks for fixing a long standing issue.
Tested-by: Petr Vorel <pvorel@suse.cz>
(on openSUSE and SLES)
Kind regards,
Petr
next prev parent reply other threads:[~2023-03-28 13:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-13 11:23 [pynfs PATCH v2 0/5] An assortment of pynfs patches Jeff Layton
2023-03-13 11:23 ` [pynfs PATCH v2 1/5] nfs4.0: add a retry loop on NFS4ERR_DELAY to compound function Jeff Layton
2023-03-13 11:23 ` [pynfs PATCH v2 2/5] examples: add a new example localhost_helper.sh script Jeff Layton
2023-03-13 11:23 ` [pynfs PATCH v2 3/5] nfs4.0/testserver.py: don't return an error when tests fail Jeff Layton
2023-03-13 11:24 ` [pynfs PATCH v2 4/5] testserver.py: add a new (special) "everything" flag Jeff Layton
2023-03-13 11:24 ` [pynfs PATCH v2 5/5] LOCK24: fix the lock_seqid in second lock request Jeff Layton
2023-03-13 18:51 ` Frank Filz
2023-03-13 21:23 ` Jeff Layton
2023-04-13 18:35 ` Calum Mackay
2023-04-14 14:41 ` Frank Filz
2023-04-14 17:24 ` Calum Mackay
2023-03-28 13:23 ` Petr Vorel [this message]
2023-03-13 16:39 ` [pynfs PATCH v2 0/5] An assortment of pynfs patches Calum Mackay
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=20230328132307.GA780540@pevik \
--to=pvorel@suse.cz \
--cc=bfields@fieldses.org \
--cc=calum.mackay@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 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.