From: Joe Perches <joe@perches.com>
To: SeongJae Park <sj38.park@gmail.com>, akpm@linux-foundation.org
Cc: SeongJae Park <sjpark@amazon.de>,
Jonathan.Cameron@Huawei.com, acme@kernel.org,
alexander.shishkin@linux.intel.com, amit@kernel.org,
benh@kernel.crashing.org, brendanhiggins@google.com,
corbet@lwn.net, david@redhat.com, dwmw@amazon.com,
elver@google.com, fan.du@intel.com, foersleo@amazon.de,
greg@kroah.com, gthelen@google.com, guoju.fgj@alibaba-inc.com,
jgowans@amazon.com, mgorman@suse.de, mheyne@amazon.de,
minchan@kernel.org, mingo@redhat.com, namhyung@kernel.org,
peterz@infradead.org, riel@surriel.com, rientjes@google.com,
rostedt@goodmis.org, rppt@kernel.org, shakeelb@google.com,
shuah@kernel.org, sieberf@amazon.com, snu@zelle79.org,
vbabka@suse.cz, vdavydov.dev@gmail.com, zgf574564920@gmail.com,
linux-damon@amazon.com, linux-mm@kvack.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v33 13/13] MAINTAINERS: Update for DAMON
Date: Tue, 13 Jul 2021 09:49:53 -0700 [thread overview]
Message-ID: <bf25e7b270fb247475254254fece22cf6abbd0ef.camel@perches.com> (raw)
In-Reply-To: <20210713123356.6924-14-sj38.park@gmail.com>
On Tue, 2021-07-13 at 12:33 +0000, SeongJae Park wrote:
> From: SeongJae Park <sjpark@amazon.de>
>
> This commit updates MAINTAINERS file for DAMON related files.
>
> Signed-off-by: SeongJae Park <sjpark@amazon.de>
> Reviewed-by: Markus Boehme <markubo@amazon.de>
> ---
> MAINTAINERS | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index a61f4f3b78a9..d492ae8b77de 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -5114,6 +5114,18 @@ F: net/ax25/ax25_out.c
> F: net/ax25/ax25_timer.c
> F: net/ax25/sysctl_net_ax25.c
>
>
> +DATA ACCESS MONITOR
> +M: SeongJae Park <sjpark@amazon.de>
> +L: linux-mm@kvack.org
> +S: Maintained
> +F: Documentation/admin-guide/mm/damon/*
> +F: Documentation/vm/damon/*
> +F: include/linux/damon.h
> +F: include/trace/events/damon.h
> +F: mm/damon/*
> +F: tools/damon/*
> +F: tools/testing/selftests/damon/*
Using "F: <path>/*" means that you are maintaining only
files in that specific path and not any subdirectory of that path.
Are there subdirectories in these uses of <path>/*
that you are avoiding?
If not, the proper use is just a trailing forward slash like
F: <path>/
I believe this should be:
DATA ACCESS MONITOR
M: SeongJae Park <sjpark@amazon.de>
L: linux-mm@kvack.org
S: Maintained
F: Documentation/admin-guide/mm/damon/
F: Documentation/vm/damon/
F: include/linux/damon.h
F: include/trace/events/damon.h
F: mm/damon/
F: tools/damon/
F: tools/testing/selftests/damon/
next prev parent reply other threads:[~2021-07-13 16:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-13 12:33 [PATCH v33 00/13] Introduce Data Access MONitor (DAMON) SeongJae Park
2021-07-13 12:33 ` [PATCH v33 01/13] mm: " SeongJae Park
2021-07-13 12:33 ` [PATCH v33 02/13] mm/damon/core: Implement region-based sampling SeongJae Park
2021-07-13 12:33 ` [PATCH v33 03/13] mm/damon: Adaptively adjust regions SeongJae Park
2021-07-13 12:33 ` [PATCH v33 04/13] mm/idle_page_tracking: Make PG_idle reusable SeongJae Park
2021-07-13 12:33 ` [PATCH v33 05/13] mm/damon: Implement primitives for the virtual memory address spaces SeongJae Park
2021-07-13 12:33 ` [PATCH v33 06/13] mm/damon: Add a tracepoint SeongJae Park
2021-07-13 12:33 ` [PATCH v33 07/13] mm/damon: Implement a debugfs-based user space interface SeongJae Park
2021-07-13 12:33 ` [PATCH v33 08/13] mm/damon/dbgfs: Export kdamond pid to the user space SeongJae Park
2021-07-13 12:33 ` [PATCH v33 09/13] mm/damon/dbgfs: Support multiple contexts SeongJae Park
2021-07-13 12:33 ` [PATCH v33 10/13] Documentation: Add documents for DAMON SeongJae Park
2021-07-13 12:33 ` [PATCH v33 11/13] mm/damon: Add kunit tests SeongJae Park
2021-07-13 12:33 ` [PATCH v33 12/13] mm/damon: Add user space selftests SeongJae Park
2021-07-13 12:33 ` [PATCH v33 13/13] MAINTAINERS: Update for DAMON SeongJae Park
2021-07-13 16:49 ` Joe Perches [this message]
2021-07-13 17:05 ` SeongJae Park
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=bf25e7b270fb247475254254fece22cf6abbd0ef.camel@perches.com \
--to=joe@perches.com \
--cc=Jonathan.Cameron@Huawei.com \
--cc=acme@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=amit@kernel.org \
--cc=benh@kernel.crashing.org \
--cc=brendanhiggins@google.com \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dwmw@amazon.com \
--cc=elver@google.com \
--cc=fan.du@intel.com \
--cc=foersleo@amazon.de \
--cc=greg@kroah.com \
--cc=gthelen@google.com \
--cc=guoju.fgj@alibaba-inc.com \
--cc=jgowans@amazon.com \
--cc=linux-damon@amazon.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@suse.de \
--cc=mheyne@amazon.de \
--cc=minchan@kernel.org \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=rppt@kernel.org \
--cc=shakeelb@google.com \
--cc=shuah@kernel.org \
--cc=sieberf@amazon.com \
--cc=sj38.park@gmail.com \
--cc=sjpark@amazon.de \
--cc=snu@zelle79.org \
--cc=vbabka@suse.cz \
--cc=vdavydov.dev@gmail.com \
--cc=zgf574564920@gmail.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;
as well as URLs for NNTP newsgroup(s).