All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ethan Tidmore" <ethantidmore06@gmail.com>
To: "Linus Probert" <linus.probert@gmail.com>,
	"Julia Lawall" <julia.lawall@inria.fr>
Cc: "Dan Carpenter" <error27@gmail.com>,
	"Robert P. J. Day" <rpjday@crashcourse.ca>,
	<kernel-janitors@vger.kernel.org>
Subject: Re: Status of kernel-janitors?
Date: Sat, 04 Apr 2026 11:29:42 -0500	[thread overview]
Message-ID: <DHKIHCMOORTC.SSZLY4MXWBH5@gmail.com> (raw)
In-Reply-To: <DHJTVEP7FY8Y.1L1C3P9RYRR0L@gmail.com>

On Fri Apr 3, 2026 at 4:12 PM CDT, Linus Probert wrote:
> On Fri Apr 3, 2026 at 2:01 AM CEST, Julia Lawall wrote:
>
> [...]
>
>> You can use the get_maintainer.pl script to find out who could be
>> interested.  You could use the following options to avoid getting too many
>> people:
>>
>> --nokeywords --nogit --nogit-fallback --norolestats
>
> Thanks. That's the command I've been using.
>
> I submitted it to the listed emails and it got merged. My concern was
> that the patch being written on staging-testing might not merge with
> whatever branch it now got applied to.

Typically linux-next is want you'd want to use here.

Thanks,

ET

>
> I guess it was fine.
>
> Br,
> Linus


      parent reply	other threads:[~2026-04-04 16:29 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 12:10 Status of kernel-janitors? Linus Probert
2026-03-30 12:25 ` Dan Carpenter
2026-03-30 12:51   ` Linus Probert
2026-03-30 13:27 ` Robert P. J. Day
2026-03-30 20:32   ` Linus Probert
2026-03-30 20:48   ` Dan Carpenter
2026-03-30 21:09     ` Robert P. J. Day
2026-04-02 21:57     ` Linus Probert
2026-04-03  0:01       ` Julia Lawall
2026-04-03 21:12         ` Linus Probert
2026-04-03 22:20           ` Rolf Reintjes
2026-04-03 22:26             ` Linus Probert
2026-04-04 16:29           ` Ethan Tidmore [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=DHKIHCMOORTC.SSZLY4MXWBH5@gmail.com \
    --to=ethantidmore06@gmail.com \
    --cc=error27@gmail.com \
    --cc=julia.lawall@inria.fr \
    --cc=kernel-janitors@vger.kernel.org \
    --cc=linus.probert@gmail.com \
    --cc=rpjday@crashcourse.ca \
    /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.