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

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