All of lore.kernel.org
 help / color / mirror / Atom feed
From: SeongJae Park <sj@kernel.org>
To: Vishal Moola <vishal.moola@gmail.com>
Cc: SeongJae Park <sj@kernel.org>,
	damon@lists.linux.dev, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org
Subject: Re: [PATCH] MAINTAINERS: add sashiko as the first DAMON reviewer
Date: Wed,  1 Apr 2026 12:52:12 -0700	[thread overview]
Message-ID: <20260401195213.68900-1-sj@kernel.org> (raw)
In-Reply-To: <ac1fOrrURjCfQyJY@fedora>

On Wed, 1 Apr 2026 11:08:58 -0700 Vishal Moola <vishal.moola@gmail.com> wrote:

> On Wed, Apr 01, 2026 at 09:26:36AM -0700, SeongJae Park wrote:
> > sashiko did arguably good jobs at reviewing DAMON patches, for multiple
> > cases.  "Today" is the greatest day to give sashiko a credit and the
> > responsibility.  Add sashiko to MAINTAINERS file as a DAMON reviewer.
> 
> This is a great idea! Andrew should add it to the MM one too :P

Why not 'THE REST'? ;)

> 
> > ---
> >  MAINTAINERS | 1 +
> >  1 file changed, 1 insertion(+)
> > 
> > diff --git a/MAINTAINERS b/MAINTAINERS
> > index 16874c32e288..42aeaa858531 100644
> > --- a/MAINTAINERS
> > +++ b/MAINTAINERS
> > @@ -7041,6 +7041,7 @@ F:	drivers/platform/x86/dasharo-acpi.c
> >  
> >  DAMON
> >  M:	SeongJae Park <sj@kernel.org>
> > +R:	sashiko.dev
> 
> Maybe we should give it a kernel.org address while we're at it. It would
> look more in place.

Oh, so that it could use kernel.org infra, right?  Good idea, but asking
kernel.org address might take too much time.  I will move fast and break things
by sharing my GPG key with sashiko!


Thanks,
sj

      reply	other threads:[~2026-04-01 19:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-01 16:26 [PATCH] MAINTAINERS: add sashiko as the first DAMON reviewer SeongJae Park
2026-04-01 18:08 ` Vishal Moola
2026-04-01 19:52   ` SeongJae Park [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=20260401195213.68900-1-sj@kernel.org \
    --to=sj@kernel.org \
    --cc=damon@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vishal.moola@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 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.