From: Yanjun Zhu <yanjun.zhu@oracle.com>
To: "Tantilov, Emil S" <emil.s.tantilov@intel.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH 1/1] ixgbe: add the external ixgbe fiber transceiver status
Date: Fri, 10 Feb 2017 10:43:59 +0800 [thread overview]
Message-ID: <589D28EF.1050602@oracle.com> (raw)
In-Reply-To: <87618083B2453E4A8714035B62D679925074E73F@FMSMSX105.amr.corp.intel.com>
On 2017/2/10 3:08, Tantilov, Emil S wrote:
>> -----Original Message-----
>> From: netdev-owner@vger.kernel.org [mailto:netdev-owner@vger.kernel.org] On
>> Behalf Of Zhu Yanjun
>> Sent: Wednesday, February 08, 2017 7:03 PM
>> To: Kirsher, Jeffrey T <jeffrey.t.kirsher@intel.com>; broonie@kernel.org;
>> davem@davemloft.net; intel-wired-lan@lists.osuosl.org;
>> netdev@vger.kernel.org
>> Subject: [PATCH 1/1] ixgbe: add the external ixgbe fiber transceiver status
>>
>> When the ixgbe fiber transceiver is external, it is necessary to get
>> the present/absent status of this external ixgbe fiber transceiver.
> The transceiver field was deprecated in the old ethtool API and is being
> removed in the new. This patch will not apply at all once those changes are made:
>
> http://patchwork.ozlabs.org/patch/725081/
Thanks for your kind reply. I will change this patch based on the above
changes.
Zhu Yanjun
>
> Thanks,
> Emil
>
>
>
prev parent reply other threads:[~2017-02-10 2:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 3:03 [PATCH 1/1] ixgbe: add the external ixgbe fiber transceiver status Zhu Yanjun
2017-02-09 3:03 ` [PATCH 1/1] ethtool: add the external transceiver status of the ixgbe fiber Zhu Yanjun
2017-02-09 10:49 ` [PATCH 1/1] ixgbe: add the external ixgbe fiber transceiver status Sergei Shtylyov
2017-02-09 19:08 ` Tantilov, Emil S
2017-02-10 2:43 ` Yanjun Zhu [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=589D28EF.1050602@oracle.com \
--to=yanjun.zhu@oracle.com \
--cc=broonie@kernel.org \
--cc=davem@davemloft.net \
--cc=emil.s.tantilov@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jeffrey.t.kirsher@intel.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).