[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b2cc74c0-d63f-418b-9c28-f7a143f61bd3@lunn.ch>
Date: Thu, 8 Jan 2026 15:31:59 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Jijie Shao <shaojijie@...wei.com>
Cc: davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org,
pabeni@...hat.com, andrew+netdev@...n.ch, horms@...nel.org,
Frank.Sae@...or-comm.com, hkallweit1@...il.com,
linux@...linux.org.uk, shenjian15@...wei.com,
liuyonglong@...wei.com, chenhao418@...wei.com,
jonathan.cameron@...wei.com, salil.mehta@...wei.com,
shiyongbang@...wei.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC net-next 2/6] net: phy: add support to set default
rules
> However, there is no way to handle the issue with another patch;
> I cannot directly modify the ACPI table (a risky operation).
It should not be risky. ACPI tables have as many bugs as any other
software. You have to assume they are buggy and will get updated
during their lifetime, so you have processes in place to allow them to
be safely upgraded.
Andrew
Powered by blists - more mailing lists