linux-kernel - Re: [PATCH v7 0/8] gpio: renesas: Add support for GPIO and related interrupts in RZ/N1 SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <aV6wcIE0D7ozKeQn@ninjato>
Date: Wed, 7 Jan 2026 20:13:52 +0100
From: Wolfram Sang <wsa+renesas@...g-engineering.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>,
	Rob Herring <robh@...nel.org>, Thomas Gleixner <tglx@...utronix.de>
Cc: "Herve Codina (Schneider Electric)" <herve.codina@...tlin.com>,
	Linus Walleij <linus.walleij@...aro.org>,
	Bartosz Golaszewski <brgl@...ev.pl>,
	Krzysztof Kozlowski <krzk+dt@...nel.org>,
	Conor Dooley <conor+dt@...nel.org>,
	Magnus Damm <magnus.damm@...il.com>,
	Saravana Kannan <saravanak@...gle.com>, linux-gpio@...r.kernel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-renesas-soc@...r.kernel.org,
	Pascal Eberhard <pascal.eberhard@...com>,
	Miquel Raynal <miquel.raynal@...tlin.com>,
	Thomas Petazzoni <thomas.petazzoni@...tlin.com>
Subject: Re: [PATCH v7 0/8] gpio: renesas: Add support for GPIO and related
 interrupts in RZ/N1 SoC


> > I think this series is ready and I would really like to see it upstream
> > soon. I wonder, however, if the path to upstream has already been
> > discussed? It touches various subsystems, so I don't see immediately who
> > should pick the whole series? Or if parts should go to different
> > subsystems offering immutable branches? I bring this up because I want
> > to avoid losing a cycle just because this is unclear...
> 
> We actually did[1]. Unfortunately that plan was never executed.
> The DTS patches I can easily take through renesas-devel, as they have
> no hard dependencies.
> For the remaining patches, I see two options:
>   A. Rob takes the first two patches, and provides an immutable branch.
>      Then Thomas takes the irqchip patches, and I take the rest.
>   B. Rob and Thomas provide acks, and I take the whole series.

B) should be the easiest for everyone. Rob, Thomas, are you okay to ack
these patches? If no reply here, maybe a resend is in place with proper
description of the suggested path upstream in the cover letter?


Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)