From: David Miller <davem@davemloft.net>
To: thomas.lendacky@amd.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net v1 0/3] amd-xgbe: AMD XGBE driver fixes 2017-02-28
Date: Thu, 02 Mar 2017 14:01:45 -0800 (PST) [thread overview]
Message-ID: <20170302.140145.1421874541145706926.davem@davemloft.net> (raw)
In-Reply-To: <a0806c50-958f-704a-e549-8b654f3787b2@amd.com>
From: Tom Lendacky <thomas.lendacky@amd.com>
Date: Thu, 2 Mar 2017 15:32:29 -0600
> On 3/2/2017 3:02 PM, David Miller wrote:
>> From: Tom Lendacky <thomas.lendacky@amd.com>
>> Date: Tue, 28 Feb 2017 15:02:42 -0600
>>
>>> This patch series addresses some issues in the AMD XGBE driver.
>>>
>>> The following fixes are included in this driver update series:
>>>
>>> - Stop the PHY before disabling and releasing device interrupts so that
>>> MDIO requests issued by the device can be properly handled
>>> - Set the MDIO communication mode on device startup, not just device
>>> probe
>>> - Do not overwrite SFP settings when mod_absent is detected
>>>
>>> This patch series is based on net.
>>
>> Series applied, thanks.
>
> Thanks David!
>
> Could you queue these fixes up against 4.10 stable. Nothing early than
> that is needed.
Ok, done.
prev parent reply other threads:[~2017-03-02 22:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 21:02 [PATCH net v1 0/3] amd-xgbe: AMD XGBE driver fixes 2017-02-28 Tom Lendacky
2017-02-28 21:02 ` [PATCH net v1 1/3] amd-xgbe: Stop the PHY before releasing interrupts Tom Lendacky
2017-02-28 21:03 ` [PATCH net v1 2/3] amd-xgbe: Be sure to set MDIO modes on device (re)start Tom Lendacky
2017-02-28 21:03 ` [PATCH net v1 3/3] amd-xgbe: Don't overwrite SFP PHY mod_absent settings Tom Lendacky
2017-03-02 21:02 ` [PATCH net v1 0/3] amd-xgbe: AMD XGBE driver fixes 2017-02-28 David Miller
2017-03-02 21:32 ` Tom Lendacky
2017-03-02 22:01 ` 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=20170302.140145.1421874541145706926.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=thomas.lendacky@amd.com \
/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).