From: Christoph Hellwig <hch@lst.de>
To: Daniel Wagner <dwagner@suse.de>
Cc: Christoph Hellwig <hch@lst.de>, Keith Busch <kbusch@kernel.org>,
"linux-nvme@lists.infradead.org" <linux-nvme@lists.infradead.org>
Subject: Re: libnvme API design
Date: Tue, 14 Oct 2025 06:20:11 +0200 [thread overview]
Message-ID: <20251014042011.GB30344@lst.de> (raw)
In-Reply-To: <46cc3fe6-e00a-4496-8fac-bb7f0d550fc4@flourine.local>
On Mon, Oct 13, 2025 at 04:22:32PM +0200, Daniel Wagner wrote:
> Or we just keep the nvme_nvm prefix. I've checked the existing callssites
> in nvme-cli for the Identify command. There are none.
For the NVM command set specific ID NS/CTRL I'd keep it. Most of the
Identify CNS values are not command set specifivc, so it won't affect
much code anyway.
next prev parent reply other threads:[~2025-10-14 4:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 11:07 libnvme API design Daniel Wagner
2025-10-10 7:26 ` Christoph Hellwig
2025-10-10 8:44 ` Daniel Wagner
2025-10-13 6:47 ` Christoph Hellwig
2025-10-13 13:02 ` Daniel Wagner
2025-10-13 14:22 ` Daniel Wagner
2025-10-14 4:20 ` Christoph Hellwig [this message]
2025-10-14 15:29 ` Daniel Wagner
2025-10-15 4:11 ` Christoph Hellwig
2025-10-14 4:20 ` Christoph Hellwig
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=20251014042011.GB30344@lst.de \
--to=hch@lst.de \
--cc=dwagner@suse.de \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.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.