linux-kernel - Re: [PATCH net-next 2/3] net: phy: qcom: qca808x: Fix WoL issue by utilizing at8031_set

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250703162316.32a9d442@fedora.home>
Date: Thu, 3 Jul 2025 16:23:16 +0200
From: Maxime Chevallier <maxime.chevallier@...tlin.com>
To: Luo Jie <quic_luoj@...cinc.com>
Cc: 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>, Paolo Abeni <pabeni@...hat.com>, "Russell King (Oracle)"
 <rmk+kernel@...linux.org.uk>, Viorel Suman <viorel.suman@....com>, Li Yang
 <leoyang.li@....com>, Wei Fang <wei.fang@....com>,
 <netdev@...r.kernel.org>, <linux-arm-msm@...r.kernel.org>,
 <linux-kernel@...r.kernel.org>, Luo Jie <luoj@....qualcomm.com>
Subject: Re: [PATCH net-next 2/3] net: phy: qcom: qca808x: Fix WoL issue by
 utilizing at8031_set_wol()

Hi,

On Thu, 3 Jul 2025 20:14:29 +0800
Luo Jie <quic_luoj@...cinc.com> wrote:

> The previous commit unintentionally removed the code responsible for
> enabling WoL via MMD3 register 0x8012 BIT5. As a result, Wake-on-LAN
> (WoL) support for the QCA808X PHY is no longer functional.
> 
> The WoL (Wake-on-LAN) feature for the QCA808X PHY is enabled via MMD3
> register 0x8012, BIT5. This implementation is aligned with the approach
> used in at8031_set_wol().
> 
> Fixes: e58f30246c35 ("net: phy: at803x: fix the wol setting functions")
> Signed-off-by: Luo Jie <quic_luoj@...cinc.com>

If this is a fix, you should target the -net tree instead -net-next :)

Maxime