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(-)

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
-- 
2.39.2

On Tue, Sep 12, 2023 at 2:29 PM Michael Walle <michael@walle.cc> wrote:

> 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>

Acked-by: Linus Walleij <linus.walleij@linaro.org>

Yours,
Linus Walleij

On Tue, Sep 12, 2023 at 2:29 PM Michael Walle <michael@walle.cc> wrote:
>
> 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.

Bart

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

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

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