linux-kernel - Re: [PATCH 0/7] Introduce PRU UART driver

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: <11048853-ec27-4d51-9188-7e701d84a3a1@kernel.org>
Date: Wed, 14 May 2025 14:30:09 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Judith Mendez <jm@...com>, Greg Kroah-Hartman
 <gregkh@...uxfoundation.org>, Jiri Slaby <jirislaby@...nel.org>
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
 Conor Dooley <conor+dt@...nel.org>, Nishanth Menon <nm@...com>,
 Santosh Shilimkar <ssantosh@...nel.org>,
 Vignesh Raghavendra <vigneshr@...com>, Tero Kristo <kristo@...nel.org>,
 Bin Liu <b-liu@...com>, Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
 Andrew Davis <afd@...com>, linux-kernel@...r.kernel.org,
 linux-serial@...r.kernel.org, devicetree@...r.kernel.org,
 linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 0/7] Introduce PRU UART driver

On 13/05/2025 23:59, Judith Mendez wrote:
> The PRU_ICSSG subsystems in am64x SoC, the PRU subsystem in am62 SoC, and
> PRU_ICSS subsystem in am335x SoC include a UART sub-module. This patch
> series introduces the driver and the corresponding binding documentation
> for this UART sub-module.
> 
> The DTS patches for adding PRU UART nodes and enabling PRU UART is added
> in this v1 version, but marked as DONOTMERGE since the patches only add
> context to this series.
> 
> This driver version has been tested on the following boards: am64x SK and
> am62x SK.
> 
> The RFC version of this driver has been previously tested on am335x SK as
> well. DTS patches for enabling PRU UART for am335x SK will be sent as a
> separate series once this series is merged.
> 
> Changes since RFC:
So this is v2 or v3. If this is confusing, just use b4 which does it for
you.

Otherwise how are we supposed to compare it with b4 diff?

Best regards,
Krzysztof