From: Christoph Hellwig <hch@lst.de>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Daniel Wagner <wagi@kernel.org>,
Hannes Reinecke <hare@suse.de>,
Chaitanya Kulkarni <kch@nvidia.com>,
Shin'ichiro Kawasaki <shinichiro.kawasaki@wdc.com>,
linux-nvme@lists.infradead.org
Subject: Re: nvme-cli & json vs blktests
Date: Mon, 19 May 2025 11:56:42 +0200 [thread overview]
Message-ID: <20250519095642.GA21183@lst.de> (raw)
In-Reply-To: <30a83f60-34eb-4940-b322-8ed31f091435@flourine.local>
On Mon, May 19, 2025 at 11:51:47AM +0200, Daniel Wagner wrote:
> On Mon, May 19, 2025 at 07:49:05AM +0200, Christoph Hellwig wrote:
> > make the nvme-cli build a little less arcane?
>
> There is no magic build into the meson/ninja build system. meson creates
> the ninja build instruction which are fully hardcoded, thus it wont pick
> up any newly installed libraries on automatically. Running meson with
> 'setup --reconfigure' is a design choice of this build system.
>
> I don't really see a problem with this approach.
The fact that a make clean is not clean enough to find newly installed
dependencies is very unusual.
next prev parent reply other threads:[~2025-05-19 10:07 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 [this message]
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
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=20250519095642.GA21183@lst.de \
--to=hch@lst.de \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=kch@nvidia.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox