| 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
| ||
|
Message-ID: <e5603fa0-0755-4b49-ad5f-9f999e8d4e3f@redhat.com> Date: Tue, 16 Jul 2024 15:14:36 +0200 From: Paolo Abeni <pabeni@...hat.com> To: Rengarajan S <rengarajan.s@...rochip.com>, woojung.huh@...rochip.com, UNGLinuxDriver@...rochip.com, davem@...emloft.net, edumazet@...gle.com, kuba@...nel.org, netdev@...r.kernel.org, linux-usb@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH v1 net-next] lan78xx: Refactor interrupt handling and redundant messages On 7/16/24 06:58, Rengarajan S wrote: > The MAC and PHY interrupt are not synchronized. When multiple phy > interrupt occur while the MAC interrupt is cleared, the phy handle > will not be called which causes the PHY interrupt to remain set > throughout. This is avoided by not clearing the MAC interrupt each > time. When the PHY interrupt is set, the MAC calls the PHY handle > and after processing the timestamp the PHY interrupt is cleared. > Also, avoided repetitive debug messages by replacing netdev_err > with netif_dbg. > > Signed-off-by: Rengarajan S <rengarajan.s@...rochip.com> ## Form letter - net-next-closed The merge window for v6.11 and therefore net-next is closed for new drivers, features, code refactoring and optimizations. We are currently accepting bug fixes only. Please repost when net-next reopens after July 29th. RFC patches sent for review only are obviously welcome at any time. See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle -- pw-bot: defer
Powered by blists - more mailing lists