From: Christoph Hellwig <hch@infradead.org>
To: Daniel Wagner <dwagner@suse.de>
Cc: Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Hannes Reinecke <hare@suse.de>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [PATCH blktests v3 0/3] Add support to run against real target
Date: Thu, 27 Jun 2024 05:03:46 -0700 [thread overview]
Message-ID: <Zn1VInQSahym_HhZ@infradead.org> (raw)
In-Reply-To: <20240627091016.12752-1-dwagner@suse.de>
On Thu, Jun 27, 2024 at 11:10:13AM +0200, Daniel Wagner wrote:
> I've added a new hook so that the default variables can be configured via the
Please make your mails readable by following the normal 73 character
limit.
Also what is more "real" about these targets? They mostly are
remote and more diverse. Maybe say arbitrary?
prev parent reply other threads:[~2024-06-27 12:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 9:10 [PATCH blktests v3 0/3] Add support to run against real target Daniel Wagner
2024-06-27 9:10 ` [PATCH blktests v3 1/3] nvme/rc: introduce remote target support Daniel Wagner
2024-06-27 9:59 ` Hannes Reinecke
2024-06-27 10:23 ` Daniel Wagner
2024-07-02 8:51 ` Shinichiro Kawasaki
2024-07-02 9:31 ` Shinichiro Kawasaki
2024-06-27 9:10 ` [PATCH blktests v3 2/3] nvme/030: only run against kernel soft target Daniel Wagner
2024-06-27 9:10 ` [PATCH blktests v3 3/3] contrib: add remote target setup/cleanup script Daniel Wagner
2024-06-27 9:28 ` [PATCH blktests v3 0/3] Add support to run against real target Hannes Reinecke
2024-06-27 12:03 ` Christoph Hellwig [this message]
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=Zn1VInQSahym_HhZ@infradead.org \
--to=hch@infradead.org \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.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).