From: Xander Huff <xander.huff@ni.com>
To: "f.fainelli@gmail.com" <f.fainelli@gmail.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Brad Mouring <brad.mouring@ni.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nathan Sullivan <nathan.sullivan@ni.com>
Subject: Re: [PATCH] phy: micrel: Reenable interrupts during on resume for ksz9031
Date: Mon, 22 Aug 2016 17:03:58 -0500 [thread overview]
Message-ID: <57BB76CE.7080606@ni.com> (raw)
In-Reply-To: <1471898618-55834-1-git-send-email-xander.huff@ni.com>
On 8/22/2016 3:43 PM, Xander Huff wrote:
> Like the ksz8081, the ksz9031 has the behavior where it will clear the interrupt
> enable bits when leaving power down. This takes advantage of the solution
> provided by f5aba91.
>
> Signed-off-by: Xander Huff <xander.huff@ni.com>
> Signed-off-by: Nathan Sullivan <nathan.sullivan@ni.com>
> Natinst-ReviewBoard-ID: 149877
> ---
> drivers/net/phy/micrel.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/phy/micrel.c b/drivers/net/phy/micrel.c
> index 053e879..885ac9c 100644
> --- a/drivers/net/phy/micrel.c
> +++ b/drivers/net/phy/micrel.c
> @@ -964,7 +964,7 @@ static struct phy_driver ksphy_driver[] = {
> .get_strings = kszphy_get_strings,
> .get_stats = kszphy_get_stats,
> .suspend = genphy_suspend,
> - .resume = genphy_resume,
> + .resume = kszphy_resume,
> }, {
> .phy_id = PHY_ID_KSZ8873MLL,
> .phy_id_mask = MICREL_PHY_ID_MASK,
>
Please disregard this patch as it was accidentally sent. Please instead refer to
my subsequent email with the subject:
"[PATCH] phy: micrel: Reenable interrupts during resume for ksz9031"
--
Xander Huff
Staff Software Engineer
National Instruments
prev parent reply other threads:[~2016-08-22 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 20:43 [PATCH] phy: micrel: Reenable interrupts during on resume for ksz9031 Xander Huff
2016-08-22 22:03 ` Xander Huff [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=57BB76CE.7080606@ni.com \
--to=xander.huff@ni.com \
--cc=brad.mouring@ni.com \
--cc=f.fainelli@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathan.sullivan@ni.com \
--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).