mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Vishal Verma <vishal@kernel.org>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>,
	Dan Williams <dan.j.williams@intel.com>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Dave Jiang <dave.jiang@intel.com>,
	Ira Weiny <ira.weiny@intel.com>
Cc: linux-nvdimm@lists.01.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC] MAINTAINERS: clarify maintenance of nvdimm testing tool
Date: Sat, 01 Feb 2020 13:03:08 -0700	[thread overview]
Message-ID: <0e09387cd5f2df5f19c9aa5494cc9be2ff7c14de.camel@kernel.org> (raw)
In-Reply-To: <20200201170933.924-1-lukas.bulwahn@gmail.com>

On Sat, 2020-02-01 at 18:09 +0100, Lukas Bulwahn wrote:
> The git history shows that the files under ./tools/testing/nvdimm are
> being developed and maintained by the LIBNVDIMM maintainers.
> 
> This was identified with a small script that finds all files only
> belonging to "THE REST" according to the current MAINTAINERS file, and I
> acted upon its output.
> 
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
> ---
> This is a RFC patch based on what I could see as an outsider to nvdimm.
> Dan, please pick this patch if it reflects the real responsibilities.
> 
> applies cleanly on current master and next-20200131
> 
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)

Looks good, thanks for catching this, Lukas.

Reviewed-by: Vishal Verma <vishal.l.verma@intel.com>

> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 1f77fb8cdde3..929386123257 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9564,6 +9564,7 @@ F:	drivers/acpi/nfit/*
>  F:	include/linux/nd.h
>  F:	include/linux/libnvdimm.h
>  F:	include/uapi/linux/ndctl.h
> +F:	tools/testing/nvdimm/
>  
>  LICENSES and SPDX stuff
>  M:	Thomas Gleixner <tglx@linutronix.de>



      parent reply	other threads:[~2020-02-01 20:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-01 17:09 Lukas Bulwahn
2020-02-01 17:34 ` Dan Williams
2020-02-01 20:03 ` Vishal Verma [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=0e09387cd5f2df5f19c9aa5494cc9be2ff7c14de.camel@kernel.org \
    --to=vishal@kernel.org \
    --cc=dan.j.williams@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=ira.weiny@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvdimm@lists.01.org \
    --cc=lukas.bulwahn@gmail.com \
    --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

Powered by JetHome