From: Andreas Hindborg <a.hindborg@kernel.org>
To: Christian Brauner <brauner@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Breno Leitao <leitao@debian.org>
Subject: Re: [PATCH] MAINTAINERS: configfs: add Andreas Hindborg as maintainer
Date: Sun, 06 Apr 2025 11:28:15 +0200 [thread overview]
Message-ID: <871pu5vdu8.fsf@kernel.org> (raw)
In-Reply-To: <Z_GSpcn3bMRStzf4@google.com> (Joel Becker's message of "Sat, 05 Apr 2025 13:29:25 -0700")
Hi Joel,
"Joel Becker" <jlbec@evilplan.org> writes:
> On Fri, Apr 04, 2025 at 10:42:29AM +0200, Christian Brauner wrote:
>> On Thu, Apr 03, 2025 at 11:47:23PM -0700, Christoph Hellwig wrote:
>> > On Thu, Apr 03, 2025 at 01:27:27PM +0200, Christian Brauner wrote:
>> > > There's no need to get upset. Several people pointed out that Joel
>> > > Becker retired and since he hasn't responded this felt like the right
>> > > thing to do. Just send a patch to add him back. I see no reason to not
>> > > have Andreas step up to maintain it.
>> >
>> > Removing someone just because they have retired feels odd, but hey who
>> > am I to complain. I did reach out to him when giving maintainership
>> > and he replied although it did indeed take a while.
>>
>> I mean, we can surely put Joel back in. My take would be to remove
>> that person from the maintainer entry because people will get confused
>> when they don't receive a reply. But I'm totally fine if we should leave
>> Joel in.
>
> Howdy folks,
>
> I do apologize for my delayed responses. I try to review patches as I
> find them, but I haven't yet set up a dedicated tree -- a bit out of
> practice.
How would you like the maintainer entry to look:
- Are you OK with me taking up maintenance of configfs?
- If yes,
- would you like to be added as a reviewer?
- would you prefer to be listed as co-maintainer?
- If no,
- would you have me as a co-maintainer?
- or would you have me as a reviewer?
I set up a tree according to the patch I submitted. I did not switch out
linux-next yet, but I was about to send a request to do that. I will
stall that pending your response on the above.
> The Rust patches gave me pause. I have no context to review them --
> even the little Rust I am familiar with looks nothing like the complex
> stuff the kernel bindings are doing. For that part, all I can do is
> hope someone other than I knows what the Rust should be doing.
That job is part of what I just signed up for, so we have that covered.
If you do not want/need my help in maintaining the C part of configfs,
we can add a sub-entry for the rust parts.
Best regards,
Andreas Hindborg
next prev parent reply other threads:[~2025-04-06 9:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-26 16:45 [PATCH] MAINTAINERS: configfs: add Andreas Hindborg as maintainer Andreas Hindborg
2025-03-28 9:14 ` Christian Brauner
2025-03-28 11:09 ` Christoph Hellwig
2025-03-28 16:23 ` Andreas Hindborg
2025-04-03 11:27 ` Christian Brauner
2025-04-04 6:47 ` Christoph Hellwig
2025-04-04 8:42 ` Christian Brauner
2025-04-05 20:29 ` Joel Becker
2025-04-06 9:28 ` Andreas Hindborg [this message]
2025-04-22 13:26 ` Andreas Hindborg
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=871pu5vdu8.fsf@kernel.org \
--to=a.hindborg@kernel.org \
--cc=brauner@kernel.org \
--cc=hch@infradead.org \
--cc=leitao@debian.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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