From: Nilay Shroff <nilay@linux.ibm.com>
To: Guixin Liu <kanie@linux.alibaba.com>,
Keith Busch <kbusch@kernel.org>, Jens Axboe <axboe@kernel.dk>,
Christoph Hellwig <hch@lst.de>, Sagi Grimberg <sagi@grimberg.me>,
Daniel Wagner <dwagner@suse.de>,
John Garry <john.g.garry@oracle.com>,
Hannes Reinecke <hare@suse.de>
Cc: 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: Mon, 6 Jul 2026 14:11:39 +0530 [thread overview]
Message-ID: <269ae1ee-5f41-47f6-ad00-8a87e77e7e21@linux.ibm.com> (raw)
In-Reply-To: <20260706023439.3054578-4-kanie@linux.alibaba.com>
On 7/6/26 8:04 AM, Guixin Liu wrote:
> Add documentation file entries that were missing from the NVM EXPRESS
> DRIVER and NVM EXPRESS TARGET DRIVER sections, so patches touching
> these files are properly routed to the NVMe mailing list and
> maintainers.
>
> Signed-off-by: Guixin Liu<kanie@linux.alibaba.com>
> Reviewed-by: Hannes Reinecke<hare@kernel.org>
> ---
> MAINTAINERS | 4 ++++
> 1 file changed, 4 insertions(+)
Looks good to me.
Reviewed-by: Nilay Shroff <nilay@linux.ibm.com>
prev parent reply other threads:[~2026-07-06 8:42 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
2026-07-06 8:41 ` Nilay Shroff [this message]
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=269ae1ee-5f41-47f6-ad00-8a87e77e7e21@linux.ibm.com \
--to=nilay@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=dwagner@suse.de \
--cc=hare@suse.de \
--cc=hch@lst.de \
--cc=john.g.garry@oracle.com \
--cc=kanie@linux.alibaba.com \
--cc=kbusch@kernel.org \
--cc=linux-nvme@lists.infradead.org \
--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.