lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <871pu5vdu8.fsf@kernel.org>
Date: Sun, 06 Apr 2025 11:28:15 +0200
From: Andreas Hindborg <a.hindborg@...nel.org>
To: Christian Brauner <brauner@...nel.org>
Cc: Christoph Hellwig <hch@...radead.org>,  linux-fsdevel@...r.kernel.org,
  linux-kernel@...r.kernel.org,  Breno Leitao <leitao@...ian.org>
Subject: Re: [PATCH] MAINTAINERS: configfs: add Andreas Hindborg as maintainer

Hi Joel,

"Joel Becker" <jlbec@...lplan.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



Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ