mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Lorenzo Stoakes (Oracle)" <ljs@kernel.org>
To: Josh Law <hlcj1234567@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	 linux-kernel@vger.kernel.org, Josh Law <objecting@objecting.org>
Subject: Re: [PATCH] MAINTAINERS: add Josh Law as reviewer for library code
Date: Fri, 13 Mar 2026 10:17:53 +0000	[thread overview]
Message-ID: <3cd25de5-3737-49f4-aa8b-eaaee471af50@lucifer.local> (raw)
In-Reply-To: <20260307221931.2848601-1-objecting@objecting.org>

On Sat, Mar 07, 2026 at 10:19:31PM +0000, Josh Law wrote:
> Add myself as a designated reviewer for the library code to help review
> incoming patches and improvements.
>
> Signed-off-by: Josh Law <objecting@objecting.org>

Sorry but NAK, I appreciate your enthusiasm but this is literally _all_
library code, and you don't have a long track history in the kernel.

Also in [0], [1], etc. you aren't demonstrating a great deal of maturity,
so I don't think it's appropriate for you to be added at this time.

I really don't think a 'catch all' category should be getting arbitrary
extra reviewers in any case.

Please take some time to contribute to the kernel, establish yourself, and
then look to reviewership for a specific category.

Thanks, Lorenzo

> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 96e97d25e1c2..8fd03ab9c657 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -14613,6 +14613,7 @@ F:	tools/testing/nvdimm/
>
>  LIBRARY CODE
>  M:	Andrew Morton <akpm@linux-foundation.org>
> +R:	Josh Law <objecting@objecting.org>
>  L:	linux-kernel@vger.kernel.org
>  S:	Supported
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm.git mm-nonmm-unstable
> --
> 2.43.0
>
>

[0]:https://lore.kernel.org/all/c41dbb9d-b8a5-4b5f-9f71-3fe1bed210b6@gmail.com/
[1]:https://lore.kernel.org/linux-mm/40767ecf-7e25-48f5-a604-c43b835b6b66@gmail.com/

  reply	other threads:[~2026-03-13 10:17 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-07 22:19 Josh Law
2026-03-13 10:17 ` Lorenzo Stoakes (Oracle) [this message]
2026-03-13 10:49   ` Vlastimil Babka
2026-03-07 22:21     ` [PATCH v2] " Josh Law
     [not found]       ` <667b75ad-bce9-4997-8ebf-8077952c2797@gmail.com>
2026-03-13 15:00         ` [PATCH] " Christian Brauner
2026-03-13 15:33           ` Christian Brauner
2026-03-13 15:48             ` Lorenzo Stoakes (Oracle)
2026-03-13 15:51               ` Josh Law
2026-03-13 15:56                 ` Lorenzo Stoakes (Oracle)
2026-03-13 15:56                 ` Jens Axboe
2026-03-13 16:00                   ` Josh Law
2026-03-13 16:06                     ` Jens Axboe
2026-03-13 15:52             ` Darrick J. Wong
2026-03-13 15:54               ` Josh Law

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=3cd25de5-3737-49f4-aa8b-eaaee471af50@lucifer.local \
    --to=ljs@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=hlcj1234567@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=objecting@objecting.org \
    /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