From: "bfields@fieldses.org" <bfields@fieldses.org>
To: dai.ngo@oracle.com
Cc: Trond Myklebust <trondmy@hammerspace.com>,
"chuck.lever@oracle.com" <chuck.lever@oracle.com>,
"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>,
"linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCH RFC v6 2/2] nfsd: Initial implementation of NFSv4 Courteous Server
Date: Wed, 8 Dec 2021 12:45:26 -0500 [thread overview]
Message-ID: <20211208174526.GB29555@fieldses.org> (raw)
In-Reply-To: <cdf6317b-aa42-539a-bc7f-3150e83cbc60@oracle.com>
On Wed, Dec 08, 2021 at 09:29:31AM -0800, dai.ngo@oracle.com wrote:
> Do you know if there is an option to specify a list of tests to run,
> instead of 'all'?
Yes, you can list the tests. See the --help, --showflags, and
--showcodes options to testserver.py.
--b.
next prev parent reply other threads:[~2021-12-08 17:45 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 17:59 [PATCH RFC v6 0/2] nfsd: Initial implementation of NFSv4 Courteous Server Dai Ngo
2021-12-06 17:59 ` [PATCH RFC v6 1/2] fs/lock: add new callback, lm_expire_lock, to lock_manager_operations Dai Ngo
2021-12-06 18:39 ` Chuck Lever III
2021-12-06 19:52 ` Trond Myklebust
2021-12-06 20:05 ` bfields
2021-12-06 20:36 ` dai.ngo
2021-12-06 22:05 ` Trond Myklebust
2021-12-06 23:07 ` dai.ngo
2021-12-06 17:59 ` [PATCH RFC v6 2/2] nfsd: Initial implementation of NFSv4 Courteous Server Dai Ngo
2021-12-06 19:55 ` Chuck Lever III
2021-12-06 21:44 ` dai.ngo
2021-12-06 22:30 ` Chuck Lever III
2021-12-06 22:52 ` Bruce Fields
2021-12-07 22:00 ` Chuck Lever III
2021-12-07 22:35 ` Bruce Fields
2021-12-08 15:17 ` Chuck Lever III
2021-12-08 15:54 ` dai.ngo
2021-12-08 15:58 ` Chuck Lever III
2021-12-08 16:16 ` Trond Myklebust
2021-12-08 16:25 ` dai.ngo
2021-12-08 16:39 ` bfields
2021-12-08 17:29 ` dai.ngo
2021-12-08 17:45 ` bfields [this message]
2021-12-10 17:51 ` dai.ngo
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=20211208174526.GB29555@fieldses.org \
--to=bfields@fieldses.org \
--cc=chuck.lever@oracle.com \
--cc=dai.ngo@oracle.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.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