[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <f46b186a-b317-4b3d-82fa-793242b323f6@gmail.com>
Date: Fri, 20 Dec 2024 23:14:20 +0100
From: Heiner Kallweit <hkallweit1@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Andrew Lunn <andrew@...n.ch>, tony@...mide.com, robh@...nel.org,
krzk+dt@...nel.org, conor+dt@...nel.org, linux@...linux.org.uk,
andrew+netdev@...n.ch, pabeni@...hat.com, davem@...emloft.net,
edumazet@...gle.com, horms@...nel.org, linux-omap@...r.kernel.org,
devicetree@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/3] net: add and use phy_disable_eee
On 20.12.2024 15:25, Jakub Kicinski wrote:
> On Fri, 20 Dec 2024 09:40:38 +0100 Andrew Lunn wrote:
>>> Patch 3 is marked "not applicable" in patchwork and didn't make it to net-next.
>>> Any issue with this patch?
>>
>> Maybe Jakub wants you to submit it to the TI DT Maintainer? Or get an
>> Acked-by: from said Maintainer.
>
> Indeed, we got screamed at once for applying dts changes.
> I filter them out now 🤷️ Sorry for not letting you know.
OK, thanks for the explanation. Then I hope Tony as TI Omap DT maintainer
picks it up.
Powered by blists - more mailing lists