Linux Documentation
 help / color / mirror / Atom feed
From: Dave Jiang <dave.jiang@intel.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	Dan Williams <djbw@kernel.org>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <ira.weiny@intel.com>, Jonathan Corbet <corbet@lwn.net>,
	Shuah Khan <skhan@linuxfoundation.org>,
	nvdimm@lists.linux.dev, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: nvdimm: Include maintainer profile
Date: Mon, 18 May 2026 08:43:53 -0700	[thread overview]
Message-ID: <3d2755da-d94d-4db8-895d-1c591545ef66@intel.com> (raw)
In-Reply-To: <20260518104306.39289-2-krzysztof.kozlowski@oss.qualcomm.com>



On 5/18/26 3:43 AM, Krzysztof Kozlowski wrote:
> No dedicated NVDIMM maintainers are returned by get_maintainers.pl for
> the subsystem maintainer profile, thus patches changing that file miss
> the actual owners of the file.
> 
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>

Acked-by: Dave Jiang <dave.jiang@intel.com>


> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 7a65b220d93f..294909f6d488 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14751,6 +14751,7 @@ S:	Supported
>  Q:	https://patchwork.kernel.org/project/linux-nvdimm/list/
>  P:	Documentation/nvdimm/maintainer-entry-profile.rst
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm.git
> +F:	Documentation/nvdimm/maintainer-entry-profile.rst
>  F:	drivers/acpi/nfit/*
>  F:	drivers/nvdimm/*
>  F:	include/linux/libnvdimm.h


  reply	other threads:[~2026-05-18 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-18 10:43 [PATCH] MAINTAINERS: nvdimm: Include maintainer profile Krzysztof Kozlowski
2026-05-18 15:43 ` Dave Jiang [this message]
2026-06-02  1:18 ` Alison Schofield

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=3d2755da-d94d-4db8-895d-1c591545ef66@intel.com \
    --to=dave.jiang@intel.com \
    --cc=corbet@lwn.net \
    --cc=djbw@kernel.org \
    --cc=ira.weiny@intel.com \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --cc=skhan@linuxfoundation.org \
    --cc=vishal.l.verma@intel.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