[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <080be4a402fe3e65a4e09070c0243b6887b6f9ae.camel@redhat.com>
Date: Thu, 09 May 2024 11:18:01 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: Daniel Golle <daniel@...rotopia.org>, Andrew Lunn <andrew@...n.ch>,
Heiner Kallweit <hkallweit1@...il.com>, Russell King
<linux@...linux.org.uk>, "David S. Miller" <davem@...emloft.net>, Eric
Dumazet <edumazet@...gle.com>, Jakub Kicinski <kuba@...nel.org>, SkyLake
Huang <skylake.huang@...iatek.com>, Eric Woudstra <ericwouds@...il.com>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org
Cc: John Crispin <john@...ozen.org>
Subject: Re: [PATCH net] net: phy: air_en8811h: reset netdev rules when LED
is set manually
Hi,
On Wed, 2024-05-08 at 01:51 +0100, Daniel Golle wrote:
> Setting LED_OFF via the brightness_set should deactivate hw control,
> so make sure netdev trigger rules also get cleared in that case.
> This matches the behaviour when using the 'netdev' trigger without
> any hardware offloading and fixes unwanted memory of the default
> netdev trigger rules when another trigger (or no trigger) had been
> selected meanwhile.
>
> Fixes: 71e79430117d ("net: phy: air_en8811h: Add the Airoha EN8811H PHY driver")
> Signed-off-by: Daniel Golle <daniel@...rotopia.org>
The patch is marked for 'net' but it's actually targeting net-next,
since the air_en8811h is only there. Does not apply to 'net' so our CI
did not trigger. Could you please repost with a the correct target
tree?
Thanks,
Paolo
Powered by blists - more mailing lists