netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: hkallweit1@gmail.com
Cc: andrew@lunn.ch, f.fainelli@gmail.com, linux@armlinux.org.uk,
	netdev@vger.kernel.org
Subject: Re: [PATCH net-next 0/2] net: phy: improve phy_driver callback handle_interrupt
Date: Tue, 17 Mar 2020 20:58:43 -0700 (PDT)	[thread overview]
Message-ID: <20200317.205843.1649558746994587425.davem@davemloft.net> (raw)
In-Reply-To: <49afbad9-317a-3eff-3692-441fae3c4f49@gmail.com>

From: Heiner Kallweit <hkallweit1@gmail.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.

      parent reply	other threads:[~2020-03-18  3:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-16 21:31 [PATCH net-next 0/2] net: phy: improve phy_driver callback handle_interrupt Heiner Kallweit
2020-03-16 21:32 ` [PATCH net-next 1/2] " Heiner Kallweit
2020-03-16 21:33 ` [PATCH net-next 2/2] net: phy: mscc: consider interrupt source in interrupt handler Heiner Kallweit
2020-03-18  3:58 ` David Miller [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200317.205843.1649558746994587425.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=andrew@lunn.ch \
    --cc=f.fainelli@gmail.com \
    --cc=hkallweit1@gmail.com \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).