[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f783cf9c-9f79-4680-a6e9-d078abbd96ec@nvidia.com>
Date: Thu, 6 Mar 2025 11:30:53 +0000
From: Jon Hunter <jonathanh@...dia.com>
To: "Russell King (Oracle)" <linux@...linux.org.uk>,
Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>
Cc: Alexandre Torgue <alexandre.torgue@...s.st.com>,
Andrew Lunn <andrew+netdev@...n.ch>, "David S. Miller"
<davem@...emloft.net>, Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, linux-arm-kernel@...ts.infradead.org,
linux-stm32@...md-mailman.stormreply.com,
Maxime Coquelin <mcoquelin.stm32@...il.com>, netdev@...r.kernel.org,
Paolo Abeni <pabeni@...hat.com>, Thierry Reding <treding@...dia.com>,
"linux-tegra@...r.kernel.org" <linux-tegra@...r.kernel.org>
Subject: Re: [PATCH RFC 0/5] net: stmmac: fix resume failures due to RX clock
Hi Russell,
On 27/02/2025 14:37, Russell King (Oracle) wrote:
> Hi,
>
> This series is likely dependent on the "net: stmmac: cleanup transmit
> clock setting" series which was submitted earlier today.
I tested this series without the above on top of mainline and I still
saw some issues with suspend. However, when testing this on top of -next
(which has the referenced series) it works like a charm. So yes it does
appear to be dependent indeed.
I have tested this on Tegra186, Tegra194 and Tegra234 with -next and all
are working fine. So with that feel free to add my ...
Tested-by: Jon Hunter <jonathanh@...dia.com>
Thanks!
Jon
--
nvpublic
Powered by blists - more mailing lists