Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.35 as permitted sender) client-ip=23.128.96.35;
MIME-Version: 1.0
References: <20230912122850.164150-1-michael@walle.cc>
In-Reply-To: <20230912122850.164150-1-michael@walle.cc>
From:   Bartosz Golaszewski <brgl@bgdev.pl>
Date:   Tue, 12 Sep 2023 15:02:58 +0200
Message-ID: <CAMRc=Mcj77F7SZ6BxDimnD=2iXe-g02yG9KuFCKTj0m58SzOTg@mail.gmail.com>
Subject: Re: [PATCH] MAINTAINERS: gpio-regmap: make myself a maintainer of it
To:     Michael Walle <michael@walle.cc>
Cc:     Linus Walleij <linus.walleij@linaro.org>,
        linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Tue, Sep 12, 2023 at 2:29=E2=80=AFPM Michael Walle <michael@walle.cc> wr=
ote:
>
> 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
>