All of lore.kernel.org
 help / color / mirror / Atom feed
From: Daniel Gomez <da.gomez@kernel.org>
To: Aaron Tomlin <atomlin@atomlin.com>,
	mcgrof@kernel.org, petr.pavlu@suse.com, samitolvanen@google.com
Cc: linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MAINTAINERS: Add myself as reviewer for module support
Date: Sat, 18 Oct 2025 22:33:59 +0200	[thread overview]
Message-ID: <1431286d-e802-44ab-b40d-86bcfed42e3a@kernel.org> (raw)
In-Reply-To: <20251018180210.347619-1-atomlin@atomlin.com>

On 18/10/2025 20.02, Aaron Tomlin wrote:
> Voluntering as a reviewer for Module support.
> 
> Suggested-by: Luis Chamberlain <mcgrof@kernel.org>
> Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>
> ---
>  MAINTAINERS | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 545a4776795e..c6c860ccdbef 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -17392,6 +17392,7 @@ M:	Luis Chamberlain <mcgrof@kernel.org>
>  M:	Petr Pavlu <petr.pavlu@suse.com>
>  M:	Daniel Gomez <da.gomez@kernel.org>
>  R:	Sami Tolvanen <samitolvanen@google.com>
> +R:	Aaron Tomlin <atomlin@atomlin.com>
>  L:	linux-modules@vger.kernel.org
>  L:	linux-kernel@vger.kernel.org
>  S:	Maintained

Help is much appreciated.

FYI, I'm currently the one sending PRs to Linus, and I plan to send some of the
reviewed fixes next week. In addition, by the end of rc3/rc4, we'll be ready to
merge Andreas' patches with Rust module parameter support, leveraging kdevops
CI integration.

This patch, if/when acked-by the rest of the maintainers, can be merged in any
of these 2 planned PRs.

Acked-by: Daniel Gomez <da.gomez@samsung.com>

  reply	other threads:[~2025-10-18 20:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-18 18:02 [PATCH] MAINTAINERS: Add myself as reviewer for module support Aaron Tomlin
2025-10-18 20:33 ` Daniel Gomez [this message]
2025-10-18 22:27 ` Luis Chamberlain
2025-11-10 16:01 ` Daniel Gomez

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=1431286d-e802-44ab-b40d-86bcfed42e3a@kernel.org \
    --to=da.gomez@kernel.org \
    --cc=atomlin@atomlin.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-modules@vger.kernel.org \
    --cc=mcgrof@kernel.org \
    --cc=petr.pavlu@suse.com \
    --cc=samitolvanen@google.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.