From: Luis Chamberlain <mcgrof@kernel.org>
To: Petr Pavlu <petr.pavlu@suse.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Sami Tolvanen <samitolvanen@google.com>,
Daniel Gomez <da.gomez@samsung.com>,
linux-modules@vger.kernel.org, linux-kernel@vger.kernel.org,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [GIT PULL] Modules fixes for v6.14-rc5
Date: Fri, 3 Jan 2025 07:32:18 -0800 [thread overview]
Message-ID: <Z3gDAnPlA3SZEbgl@bombadil.infradead.org> (raw)
In-Reply-To: <db0cf655-906f-40e3-a9d9-d1854a6dc44b@suse.com>
On Wed, Jan 01, 2025 at 01:43:22PM +0100, Petr Pavlu wrote:
> On 12/23/24 21:14, Linus Torvalds wrote:
> > On Mon, 23 Dec 2024 at 02:55, Petr Pavlu <petr.pavlu@suse.com> wrote:
> >>
> >> Luis asked me to look after the modules maintenance for a while, with the
> >> plan to rotate it with other recently added modules maintainers/reviewers.
> >> This is my first pull request to you.
> >
> > I *really* want maintainers to give me a heads up before people change
> > and I pull from new people.
> >
> > Please? Otherwise it just takes me by surprise and looks unplanned.
>
> Sure, I think I got ahead of Luis before he was going to make you aware
> of the change.
Indeed, sorry for the lack of headsup, I forgot we can get fixes in, and
that preempted the pull request rather than waiting until the next
release.
My compromise with the Rust community was that I welcome Rust bindings
for modules and any work needed however I wanted Rust volunteers who
would step up to be both C and Rust maintainers for modules for Linux.
That call ended up with 3 new co-maintainers. To help get them exposed
to maintenance, community, process, I decided it would be good to rotate
every 6 months starting with Pavlu.
Petr is in first for rotation, next will be either Daniel Gomez or Sami
Tolvanenin. I may step out of rotation for a bit so to help give them
more exposure.
Luis
next prev parent reply other threads:[~2025-01-03 15:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-23 10:55 Petr Pavlu
2024-12-23 20:14 ` Linus Torvalds
2025-01-01 12:43 ` Petr Pavlu
2025-01-03 15:32 ` Luis Chamberlain [this message]
2024-12-24 17:30 ` pr-tracker-bot
2024-12-24 17:30 ` pr-tracker-bot
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=Z3gDAnPlA3SZEbgl@bombadil.infradead.org \
--to=mcgrof@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=da.gomez@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-modules@vger.kernel.org \
--cc=petr.pavlu@suse.com \
--cc=samitolvanen@google.com \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®