From: Christoph Hellwig <hch@lst.de>
To: Daniel Wagner <dwagner@suse.de>
Cc: Chaitanya Kulkarni <chaitanyak@nvidia.com>,
Christoph Hellwig <hch@lst.de>, Daniel Wagner <wagi@kernel.org>,
Hannes Reinecke <hare@suse.de>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: nvme-cli & json vs blktests
Date: Tue, 20 May 2025 15:34:01 +0200 [thread overview]
Message-ID: <20250520133401.GA7074@lst.de> (raw)
In-Reply-To: <a1e7dd62-b96b-4925-a9eb-d2cf181bd4f1@flourine.local>
On Tue, May 20, 2025 at 09:18:19AM +0200, Daniel Wagner wrote:
> I've updated the Makefile. The 'clean' target is now doing a proper
> cleanup and deletes all the build artifacts and configuration files.
Thanks!
next prev parent reply other threads:[~2025-05-20 13:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 5:49 nvme-cli & json vs blktests Christoph Hellwig
2025-05-19 9:51 ` Daniel Wagner
2025-05-19 9:56 ` Christoph Hellwig
2025-05-19 10:04 ` Daniel Wagner
2025-05-19 23:31 ` Chaitanya Kulkarni
2025-05-20 7:18 ` Daniel Wagner
2025-05-20 13:34 ` Christoph Hellwig [this message]
2025-05-19 11:08 ` Shinichiro Kawasaki
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=20250520133401.GA7074@lst.de \
--to=hch@lst.de \
--cc=chaitanyak@nvidia.com \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=linux-nvme@lists.infradead.org \
--cc=shinichiro.kawasaki@wdc.com \
--cc=wagi@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.