From: Guixin Liu <kanie@linux.alibaba.com>
To: Daniel Wagner <dwagner@suse.de>
Cc: Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
John Garry <john.g.garry@oracle.com>,
Nilay Shroff <nilay@linux.ibm.com>,
Hannes Reinecke <hare@suse.de>,
linux-nvme@lists.infradead.org, xlpang@linux.alibaba.com,
oliver.yang@linux.alibaba.com
Subject: Re: [PATCH 2/3] nvmet: add ABI documentation for target configfs interfaces
Date: Fri, 3 Jul 2026 09:51:13 +0800 [thread overview]
Message-ID: <74cb62d6-8003-437b-a57e-0bdbd9e9cc69@linux.alibaba.com> (raw)
In-Reply-To: <9b41ed73-9539-4e6d-bdc1-bdde4652e715@flourine.local>
在 2026/7/2 21:33, Daniel Wagner 写道:
> On Thu, Jul 02, 2026 at 11:48:44AM +0800, Guixin Liu wrote:
>> Add Documentation/ABI/testing/configfs-nvmet documenting all NVMe
> As far I am aware, nvmet is actually also used in production systems.
> Thus it's not just an testing API I think.
>
> Thanks for doing this!
>
> BTW, I agree with Hannes, grouping them together makes it easier to
> consume. Obviously they can still be sorted by time withing a group if
> this makes sense.
>
> Cheers,
> Daniel
Yes, please see the v2 patch set.
Best Regards,
Guixin Liu
next prev parent reply other threads:[~2026-07-03 1:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-02 3:48 [PATCH 0/3] nvme: add ABI documentation for sysfs and configfs interfaces Guixin Liu
2026-07-02 3:48 ` [PATCH 1/3] nvme: add ABI documentation for host sysfs interfaces Guixin Liu
2026-07-02 6:31 ` Hannes Reinecke
2026-07-02 6:50 ` Guixin Liu
2026-07-02 3:48 ` [PATCH 2/3] nvmet: add ABI documentation for target configfs interfaces Guixin Liu
2026-07-02 6:35 ` Hannes Reinecke
2026-07-02 6:51 ` Guixin Liu
2026-07-02 13:33 ` Daniel Wagner
2026-07-03 1:51 ` Guixin Liu [this message]
2026-07-02 3:48 ` [PATCH 3/3] MAINTAINERS: add missing NVMe documentation files Guixin Liu
2026-07-02 6:36 ` Hannes Reinecke
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=74cb62d6-8003-437b-a57e-0bdbd9e9cc69@linux.alibaba.com \
--to=kanie@linux.alibaba.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=nilay@linux.ibm.com \
--cc=oliver.yang@linux.alibaba.com \
--cc=sagi@grimberg.me \
--cc=xlpang@linux.alibaba.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 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.