[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2025051449-scarily-evaluator-0e03@gregkh>
Date: Wed, 14 May 2025 09:35:50 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Judith Mendez <jm@...com>
Cc: Jiri Slaby <jirislaby@...nel.org>, 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 Tue, May 13, 2025 at 04:59:27PM -0500, 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 prevents the series from being merged as our tools want to take the
whole series :(
So please, submit this in a format that we can handle. As-is, this just
makes me want to ignore it totally and focus on patch series that can be
applied. In other words, what would you do if you were in the position
of attempting to review this?
thanks,
greg k-h
Powered by blists - more mailing lists