From: Yunsheng Lin <linyunsheng@huawei.com>
To: <davem@davemloft.net>, <andrew@lunn.ch>, <f.fainelli@gmail.com>
Cc: <liguozhu@hisilicon.com>, <linuxarm@huawei.com>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<tremyfr@gmail.com>
Subject: Re: [PATCH NET v2 0/2] Add loopback support in phy_driver and hns ethtool fix
Date: Fri, 23 Jun 2017 16:18:53 +0800 [thread overview]
Message-ID: <2c145fde-eb2a-a3e6-4c3e-53b3c00ee830@huawei.com> (raw)
In-Reply-To: <1498204473-194648-1-git-send-email-linyunsheng@huawei.com>
My apology, this patch set have a bug in hns mac driver which is not
calling phy_loopback enable and disable in pair, I will send a v3 to
fix it. Please ignore this patch set.
Best Regards
Yunsheng Lin
On 2017/6/23 15:54, Lin Yun Sheng wrote:
> This Patch Set add set_loopback in phy_driver and use it to setup loopback
> when doing ethtool phy self_test.
>
> Patch V2:
> 1. Add phy_loopback in phy_device.c.
> 2. Do error checking and do the read and write once in genphy_loopback.
> 3. Remove gen10g_loopback in phy_device.c.
>
> Patch V1: Initial Submit
>
> Lin Yun Sheng (2):
> net: phy: Add phy loopback support in net phy framework
> net: hns: Use phy_driver to setup Phy loopback
>
> drivers/net/ethernet/hisilicon/hns/hns_ethtool.c | 68 +++++-------------------
> drivers/net/phy/marvell.c | 1 +
> drivers/net/phy/phy_device.c | 41 ++++++++++++++
> include/linux/phy.h | 5 ++
> 4 files changed, 61 insertions(+), 54 deletions(-)
>
prev parent reply other threads:[~2017-06-23 8:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 7:54 Lin Yun Sheng
2017-06-23 7:54 ` [PATCH NET v2 1/2] net: phy: Add phy loopback support in net phy framework Lin Yun Sheng
2017-06-23 7:54 ` [PATCH NET v2 2/2] net: hns: Use phy_driver to setup Phy loopback Lin Yun Sheng
2017-06-23 8:18 ` Yunsheng Lin [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=2c145fde-eb2a-a3e6-4c3e-53b3c00ee830@huawei.com \
--to=linyunsheng@huawei.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=tremyfr@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
all inboxes | Powered by JetHome®