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 v3 3/3] MAINTAINERS: add missing NVMe documentation files
Date: Tue, 7 Jul 2026 17:45:04 +0800 [thread overview]
Message-ID: <ef44efdb-dbc3-40ea-8bae-743e6f93884a@linux.alibaba.com> (raw)
In-Reply-To: <e2ac204c-83bf-4738-bbed-a1fffc98a678@flourine.local>
在 2026/7/7 17:20, Daniel Wagner 写道:
> On Tue, Jul 07, 2026 at 09:40:01AM +0800, Guixin Liu wrote:
>>>> so I've put them all under the testing directory for now.
>>> The NVMe APIs are definitely not in the 'testing' section. The nvmet
>>> APIs are also not in 'testing', IMO. While they are used upstream
>>> predominantly by blktests, there are also people out there using them in
>>> production systems, if we like or not.
>> You mean we can put them all under stable directory?
> Exactly, let's go ahead and put them under the stable directory.
OK，changed in v4.
Best Regards,
Guixin Liu
next prev parent reply other threads:[~2026-07-07 9:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-06 2:34 [PATCH v3 0/3] nvme: add ABI documentation for sysfs and configfs interfaces Guixin Liu
2026-07-06 2:34 ` [PATCH v3 1/3] nvme: add ABI documentation for host sysfs interfaces Guixin Liu
2026-07-06 7:46 ` Daniel Wagner
2026-07-06 8:39 ` Nilay Shroff
2026-07-06 2:34 ` [PATCH v3 2/3] nvmet: add ABI documentation for target configfs interfaces Guixin Liu
2026-07-06 8:40 ` Nilay Shroff
2026-07-06 2:34 ` [PATCH v3 3/3] MAINTAINERS: add missing NVMe documentation files Guixin Liu
2026-07-06 7:50 ` Daniel Wagner
2026-07-06 9:54 ` Guixin Liu
2026-07-06 11:55 ` Daniel Wagner
2026-07-07 1:40 ` Guixin Liu
2026-07-07 9:20 ` Daniel Wagner
2026-07-07 9:45 ` Guixin Liu [this message]
2026-07-06 8:41 ` Nilay Shroff
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=ef44efdb-dbc3-40ea-8bae-743e6f93884a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox