From: "Scariah, Thomas" <Thomas.Scariah@harman.com>
To: Andrew Lunn <andrew@lunn.ch>, Florian Fainelli <f.fainelli@gmail.com>
Cc: Thomas Scariah <thomasscariah@gmail.com>,
"nsekhar@ti.com" <nsekhar@ti.com>,
"grygorii.strashko@ti.com" <grygorii.strashko@ti.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"drivshin@allworx.com" <drivshin@allworx.com>,
"ivan.khoronzhuk@linaro.org" <ivan.khoronzhuk@linaro.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: [EXTERNAL] Re: [PATCH 1/1] ethtool : added get_phy_stats, get_strings,get_sset_count
Date: Tue, 28 Mar 2017 06:45:46 +0000 [thread overview]
Message-ID: <ad58864cd8d2474595010e6feccdb7b6@HIBDWSMB03.ad.harman.com> (raw)
In-Reply-To: <20170327173835.GD17041@lunn.ch>
Hello Andrew,
> > Hello,
> >
> > On 03/27/2017 03:12 AM, Thomas Scariah wrote:
> > > From: "Scariah, Thomas" <thomas.scariah@harman.com>
> > >
> > > Added functions to support ethtool to print the phy statistics and
> > > error information along with other ethtool statistics. This will
> > > help ethtool information to know the error is from physical layer or MAC layer.
> > > This is an enahancement for ethtool to accommodate phy statistics
> Hi Thomas
>
> What tree is this against? net-next already has get_phy_stats, get_strings, and get_sset_count in struct >phy_driver.
As I have mentioned I have developed against Kernel 4.4.14 and the similar functionality was not available.
Regards and Thanks
Thomas Scariah
-----Original Message-----
From: Andrew Lunn [mailto:andrew@lunn.ch]
Sent: Monday, March 27, 2017 11:09 PM
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Thomas Scariah <thomasscariah@gmail.com>; nsekhar@ti.com; grygorii.strashko@ti.com; davem@davemloft.net; drivshin@allworx.com; mugunthanvnm@ti.com; ivan.khoronzhuk@linaro.org; Scariah, Thomas <Thomas.Scariah@harman.com>; netdev@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: [EXTERNAL] Re: [PATCH 1/1] ethtool : added get_phy_stats, get_strings,get_sset_count
On Mon, Mar 27, 2017 at 09:44:37AM -0700, Florian Fainelli wrote:
> Hello,
>
> On 03/27/2017 03:12 AM, Thomas Scariah wrote:
> > From: "Scariah, Thomas" <thomas.scariah@harman.com>
> >
> > Added functions to support ethtool to print the phy statistics and
> > error information along with other ethtool statistics. This will
> > help ethtool information to know the error is from physical layer or MAC layer.
> > This is an enahancement for ethtool to accommodate phy statistics
Hi Thomas
What tree is this against? net-next already has get_phy_stats, get_strings, and get_sset_count in struct phy_driver.
Andrew
next prev parent reply other threads:[~2017-03-28 6:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-27 10:12 [PATCH 1/1] ethtool : added get_phy_stats,get_strings,get_sset_count Thomas Scariah
2017-03-27 16:44 ` Florian Fainelli
2017-03-27 17:26 ` Andrew Lunn
2017-03-27 17:38 ` Andrew Lunn
2017-03-28 6:45 ` Scariah, Thomas [this message]
[not found] ` <CA+1hMaGV-trVT+ZisgTtyRAVz=ZqopmwmpWyqHvWQMrkmv-96A@mail.gmail.com>
2017-03-28 12:10 ` Andrew Lunn
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=ad58864cd8d2474595010e6feccdb7b6@HIBDWSMB03.ad.harman.com \
--to=thomas.scariah@harman.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=drivshin@allworx.com \
--cc=f.fainelli@gmail.com \
--cc=grygorii.strashko@ti.com \
--cc=ivan.khoronzhuk@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=thomasscariah@gmail.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).