From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Lad, Prabhakar" <prabhakar.csengg@gmail.com>,
Linus Walleij <linusw@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
andrea.tomassetti@sipearl.com,
Geert Uytterhoeven <geert@linux-m68k.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
johan+linaro@kernel.org, LKML <linux-kernel@vger.kernel.org>,
mircea.caprioru@analog.com,
Philipp Zabel <p.zabel@pengutronix.de>,
peda@axentia.se, srini@kernel.org,
Tommaso Merciai <tommaso.merciai.xr@bp.renesas.com>,
ulf.hansson@oss.qualcomm.com,
Fabrizio Castro <fabrizio.castro.jz@renesas.com>,
Chris Paterson <Chris.Paterson2@renesas.com>
Subject: Re: [PATCH v2] mux: gpio-mux: add support for 4:1 2-channels mux
Date: Thu, 25 Jun 2026 11:43:56 +0200 [thread overview]
Message-ID: <e4cbcaa3-6980-4703-9e3c-f9b41eb2f363@kernel.org> (raw)
In-Reply-To: <CA+V-a8uqav0_xgPyfBeA9WyPFJRLFeKG+jgKw_y49OWqHhRqtg@mail.gmail.com>
On 25/06/2026 11:32, Lad, Prabhakar wrote:
> On Thu, Jun 25, 2026 at 10:15 AM Linus Walleij <linus.walleij@linaro.org> wrote:
>> Mircea from Analog Devices contributed two important drivers for
>> drivers/mux in committ
>> 8b9ce6954c05e3e4115f54444c7eaf2aa2dd5e65.
>>
>> Perhaps Analog Devices are interested in picking up and
>> maintaining drivers/mux?
>>
>> Mircea what do you say?
>>
>> Can you bring it up with your organization?
>
> Hi Linus, Krzysztof, All,
>
> While Linus mentioned Analog Devices, we at Renesas would be glad to
> step up here.
>
> I have discussed this internally, and Renesas is willing to dedicate
> the necessary engineering time to take over the active maintainership
> of drivers/mux. I am happy to act as the maintainer to review incoming
> patches, handle testing, and keep the subsystem moving forward so it
Great to hear! I appreciate. The initial pushback was a bit confusing.
> doesn't stall out. If the community is on board with this, I can send
> a patch updating the MAINTAINERS file to make it official.
Awesome, please do so. Put on CC existing maintainer (Peter), Greg and
me, change to "Maintained" (or Supported, up to you). Once you review
and collect the patches, make your tree part of Linux next and then
closer to RC5-RC6, send them as patches or pull request to Greg (Greg,
please correct me if anything here is inaccurate).
I recommend also slides from my talk from LPC 2023 - Beginner's Linux
kernel maintainer toolbox. If all this is obvious to you, then of course
apologies for lecturing.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-06-25 9:44 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-25 9:32 Lad, Prabhakar
2026-06-25 9:43 ` Krzysztof Kozlowski [this message]
2026-06-25 9:49 ` Greg Kroah-Hartman
2026-06-25 9:59 ` Lad, Prabhakar
2026-06-29 19:24 ` Linus Walleij
-- strict thread matches above, loose matches on Subject: below --
2026-05-06 7:58 [PATCH RESEND] " Linus Walleij
2026-05-06 12:33 ` [PATCH v2] " Andrea Tomassetti
2026-06-03 11:43 ` Andrea Tomassetti
2026-06-03 14:00 ` Krzysztof Kozlowski
2026-06-08 22:54 ` Linus Walleij
2026-06-17 13:09 ` Tommaso Merciai
2026-06-18 13:04 ` Linus Walleij
2026-06-18 13:27 ` Tommaso Merciai
2026-06-19 3:51 ` Krzysztof Kozlowski
2026-06-23 16:44 ` Tommaso Merciai
2026-06-24 8:59 ` Geert Uytterhoeven
2026-06-24 9:59 ` Krzysztof Kozlowski
2026-06-24 9:55 ` Krzysztof Kozlowski
2026-06-24 22:03 ` Linus Walleij
2026-06-24 22:11 ` Linus Walleij
2026-06-25 9:19 ` Nuno Sá
2026-06-29 19:27 ` Linus Walleij
2026-07-03 7:32 ` Michael Hennerich
2026-07-03 10:02 ` Miclaus, Antoniu
2026-07-03 13:19 ` Alvin Šipraga
2026-07-03 13:45 ` Lad, Prabhakar
2026-06-19 17:23 ` Srinivas Kandagatla
2026-06-30 15:08 ` Andrea Tomassetti
2026-07-03 8:10 ` Srinivas Kandagatla
2026-07-08 14:08 ` Peter Rosin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e4cbcaa3-6980-4703-9e3c-f9b41eb2f363@kernel.org \
--to=krzk@kernel.org \
--cc=Chris.Paterson2@renesas.com \
--cc=andrea.tomassetti@sipearl.com \
--cc=fabrizio.castro.jz@renesas.com \
--cc=geert@linux-m68k.org \
--cc=gregkh@linuxfoundation.org \
--cc=johan+linaro@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linusw@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mircea.caprioru@analog.com \
--cc=p.zabel@pengutronix.de \
--cc=peda@axentia.se \
--cc=prabhakar.csengg@gmail.com \
--cc=srini@kernel.org \
--cc=tommaso.merciai.xr@bp.renesas.com \
--cc=ulf.hansson@oss.qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox