From: "John W. Linville" <linville@tuxdriver.com>
To: Zhang Kang <tjbroadroad@163.com>
Cc: netdev@vger.kernel.org, Gao Wayne <Wayne.Gao@emc.com>,
Wei Net <gw_net@163.com>
Subject: Re: [PATCH] ethtool: fix MFLCN register dump for 82599 and newer
Date: Mon, 18 Dec 2017 13:38:55 -0500 [thread overview]
Message-ID: <20171218183855.GA18214@tuxdriver.com> (raw)
In-Reply-To: <20171215015651.6112-1-tjbroadroad@163.com>
On Fri, Dec 15, 2017 at 09:56:51AM +0800, Zhang Kang wrote:
> Use MFLCN for 82599 and X540 HW instead of FCTRL.
>
> Signed-off-by: Zhang Kang <tjbroadroad@163.com>
> Signed-off-by: Gao Wayne <Wayne.Gao@emc.com>
> Signed-off-by: Wei Net <gw_net@163.com>
Thanks, applied.
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2017-12-18 18:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-15 1:56 [PATCH] ethtool: fix MFLCN register dump for 82599 and newer Zhang Kang
2017-12-18 18:38 ` John W. Linville [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-13 4:43 tjbroadroad
2017-12-14 18:45 ` John W. Linville
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=20171218183855.GA18214@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=Wayne.Gao@emc.com \
--cc=gw_net@163.com \
--cc=netdev@vger.kernel.org \
--cc=tjbroadroad@163.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).