linux-kernel - Re: [PATCH] MAINTAINERS: gpio-regmap: make myself a maintainer of it

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 12 Sep 2023 15:26:22 +0200
From:   Michael Walle <michael@...le.cc>
To:     Bartosz Golaszewski <brgl@...ev.pl>
Cc:     Linus Walleij <linus.walleij@...aro.org>,
        linux-kernel@...r.kernel.org, linux-gpio@...r.kernel.org
Subject: Re: [PATCH] MAINTAINERS: gpio-regmap: make myself a maintainer of it

Hi,

>> When I've upstreamed the gpio-regmap driver, I didn't have that much
>> experience with kernel maintenance, so I've just added myself as a
>> reviewer. I've gained quite some experience, so I'd like to step up
>> as a maintainer for it.
>> 
> 
> Do you think about maintaining your own tree and sending PRs to me?
> I'm wondering if - given the little volume of changes to gpio-regmap -
> this wouldn't be unnecessary churn? I normally wait for you to Ack any
> changes to gpio-regmap code and drivers based on it anyway. Otherwise
> if it's just the formal role of the maintainer you're suggesting, then
> sure, I'm all for it.

No, no own tree, that's overkill ;) As you said, it's just some formal
change.

-michael