Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hannes Reinecke <hare@suse.de>
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>,
	Nilay Shroff <nilay@linux.ibm.com>
Cc: linux-nvme@lists.infradead.org, xlpang@linux.alibaba.com,
	oliver.yang@linux.alibaba.com
Subject: Re: [PATCH 3/3] MAINTAINERS: add missing NVMe documentation files
Date: Thu, 2 Jul 2026 08:36:08 +0200	[thread overview]
Message-ID: <897c7ba2-de2b-4603-ab51-8a9e12e4d794@suse.de> (raw)
In-Reply-To: <20260702034845.3066876-4-kanie@linux.alibaba.com>

On 7/2/26 5:48 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>
> ---
>   MAINTAINERS | 4 ++++
>   1 file changed, 4 insertions(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 15011f5752a9..7f8d52f8aab1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -19367,6 +19367,9 @@ L:	linux-nvme@lists.infradead.org
>   S:	Supported
>   W:	http://git.infradead.org/nvme.git
>   T:	git git://git.infradead.org/nvme.git
> +F:	Documentation/ABI/testing/sysfs-nvme
> +F:	Documentation/admin-guide/nvme-multipath.rst
> +F:	Documentation/fault-injection/nvme-fault-injection.rst
>   F:	Documentation/nvme/
>   F:	drivers/nvme/common/
>   F:	drivers/nvme/host/
> @@ -19409,6 +19412,7 @@ L:	linux-nvme@lists.infradead.org
>   S:	Supported
>   W:	http://git.infradead.org/nvme.git
>   T:	git git://git.infradead.org/nvme.git
> +F:	Documentation/ABI/testing/configfs-nvmet
>   F:	drivers/nvme/target/
>   
>   NVMEM FRAMEWORK

Reviewed-by: Hannes Reinecke <hare@kernel.org>

Cheers,

Hannes
-- 
Dr. Hannes Reinecke                  Kernel Storage Architect
hare@suse.de                                +49 911 74053 688
SUSE Software Solutions GmbH, Frankenstr. 146, 90461 Nürnberg
HRB 36809 (AG Nürnberg), GF: I. Totev, A. McDonald, W. Knoblich


      reply	other threads:[~2026-07-02  6:36 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
2026-07-02  3:48 ` [PATCH 3/3] MAINTAINERS: add missing NVMe documentation files Guixin Liu
2026-07-02  6:36   ` Hannes Reinecke [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=897c7ba2-de2b-4603-ab51-8a9e12e4d794@suse.de \
    --to=hare@suse.de \
    --cc=axboe@kernel.dk \
    --cc=dwagner@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=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