netdev - Re: [PATCH net-next 0/2] net: phy: improve phy_driver callback handle

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] [day] [month] [year] [list]

Message-Id: <20200317.205843.1649558746994587425.davem@davemloft.net>
Date:   Tue, 17 Mar 2020 20:58:43 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     hkallweit1@...il.com
Cc:     andrew@...n.ch, f.fainelli@...il.com, linux@...linux.org.uk,
        netdev@...r.kernel.org
Subject: Re: [PATCH net-next 0/2] net: phy: improve phy_driver callback
 handle_interrupt

From: Heiner Kallweit <hkallweit1@...il.com>
Date: Mon, 16 Mar 2020 22:31:48 +0100

> did_interrupt() clears the interrupt, therefore handle_interrupt() can
> not check which event triggered the interrupt. To overcome this
> constraint and allow more flexibility for customer interrupt handlers,
> let's decouple handle_interrupt() from parts of the phylib interrupt
> handling. Custom interrupt handlers now have to implement the
> did_interrupt() functionality in handle_interrupt() if needed.
> 
> Fortunately we have just one custom interrupt handler so far (in the
> mscc PHY driver), convert it to the changed API and make use of the
> benefits.

Series applied, thanks Heiner.