linux-kernel - Re: [PATCH v6 0/3] s32g: Use a syscon for GPR

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <20260203145438.5a850b61@kernel.org>
Date: Tue, 3 Feb 2026 14:54:38 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Paolo Abeni <pabeni@...hat.com>
Cc: Dan Carpenter <dan.carpenter@...aro.org>, Chester Lin
 <chester62515@...il.com>, Alexandre Torgue <alexandre.torgue@...s.st.com>,
 Andrew Lunn <andrew+netdev@...n.ch>, Conor Dooley <conor+dt@...nel.org>,
 "David S. Miller" <davem@...emloft.net>, devicetree@...r.kernel.org, Eric
 Dumazet <edumazet@...gle.com>, Fabio Estevam <festevam@...il.com>, Frank Li
 <Frank.Li@....com>, Ghennadi Procopciuc <ghennadi.procopciuc@....nxp.com>,
 imx@...ts.linux.dev, Jan Petrous <jan.petrous@....nxp.com>, Krzysztof
 Kozlowski <krzk+dt@...nel.org>, linux-arm-kernel@...ts.infradead.org,
 linux-kernel@...r.kernel.org, linux-stm32@...md-mailman.stormreply.com,
 Matthias Brugger <mbrugger@...e.com>, Maxime Coquelin
 <mcoquelin.stm32@...il.com>, netdev@...r.kernel.org, NXP S32 Linux Team
 <s32@....com>, Pengutronix Kernel Team <kernel@...gutronix.de>, Rob Herring
 <robh@...nel.org>, Sascha Hauer <s.hauer@...gutronix.de>,
 linaro-s32@...aro.org
Subject: Re: [PATCH v6 0/3] s32g: Use a syscon for GPR

On Tue, 3 Feb 2026 12:18:54 +0100 Paolo Abeni wrote:
> It looks like patch 3/3 depends on 1/3 but it should land in a different
> tree, as patches 1 && 2 looks suitable for 'net-next' and 3/3 should
> probably go via the arm/freescale tree.
> 
> We either need explicit ack from freescale maintainers or this should be
> split across subtrees, right?

FWIW normally we don't touch the dts patch at all, unless the
maintainer chimes in and tells us to take it. No waiting for acks.
Off the top of my head us taking dts patches only happens if 
the person posting the patch _is_ the platform maintainer..

For this series we're waiting for the bindings to be reviewed.