diff mbox series

MAINTAINERS: gpio-regmap: make myself a maintainer of it

Message ID 20230912122850.164150-1-michael@walle.cc
State Accepted
Commit 2d48c30176fa0fd61202b859d7454249f2b22bdc
Headers show
Series MAINTAINERS: gpio-regmap: make myself a maintainer of it | expand

Commit Message

Michael Walle Sept. 12, 2023, 12:28 p.m. UTC
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.

Signed-off-by: Michael Walle <michael@walle.cc>
---
 MAINTAINERS | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Comments

Bartosz Golaszewski Sept. 13, 2023, 12:10 p.m. UTC | #1
On Tue, Sep 12, 2023 at 3:26 PM Michael Walle <michael@walle.cc> wrote:
>
> 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

Fair enough, queued.

Bart
diff mbox series

Patch

diff --git a/MAINTAINERS b/MAINTAINERS
index 69de688907ca..405f616e4960 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -8872,7 +8872,7 @@  F:	drivers/gpio/gpio-mockup.c
 F:	tools/testing/selftests/gpio/
 
 GPIO REGMAP
-R:	Michael Walle <michael@walle.cc>
+M:	Michael Walle <michael@walle.cc>
 S:	Maintained
 F:	drivers/gpio/gpio-regmap.c
 F:	include/linux/gpio/regmap.h