From: Yunsheng Lin <linyunsheng@huawei.com>
To: David Miller <davem@davemloft.net>, <andrew@lunn.ch>
Cc: <f.fainelli@gmail.com>, <huangdaode@hisilicon.com>,
<xuwei5@hisilicon.com>, <liguozhu@hisilicon.com>,
<Yisen.Zhuang@huawei.com>, <gabriele.paoloni@huawei.com>,
<john.garry@huawei.com>, <linuxarm@huawei.com>,
<salil.mehta@huawei.com>, <lipeng321@huawei.com>,
<tremyfr@gmail.com>, <netdev@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH NET V7 0/2] Add loopback support in phy_driver and hns ethtool fix
Date: Fri, 30 Jun 2017 14:15:13 +0800 [thread overview]
Message-ID: <d1d49cc5-b003-baeb-7607-303b930c536f@huawei.com> (raw)
In-Reply-To: <20170629.160845.2003385325223608825.davem@davemloft.net>
Hi, David
I will send out a patch based on net-next, and
I will continue to address the problem andrew pointed
out. If I come out with a doable solution, I will send
out the new patch.
Best Regards
Yunsheng Lin
On 2017/6/30 4:08, David Miller wrote:
> From: Andrew Lunn <andrew@lunn.ch>
> Date: Thu, 29 Jun 2017 20:22:16 +0200
>
> Is less broken a sufficient criteria for acceptance?
>
> Sometimes, it depends upon the situation.
>
> If you are continuing to resolve those issues, I'll wait and
> watch for future respins then.
>
> .
>
prev parent reply other threads:[~2017-06-30 6:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 9:13 Lin Yun Sheng
2017-06-28 9:13 ` [PATCH NET V7 1/2] net: phy: Add phy loopback support in net phy framework Lin Yun Sheng
2017-06-28 13:27 ` Andrew Lunn
2017-06-29 1:35 ` Yunsheng Lin
2017-06-28 9:13 ` [PATCH NET V7 2/2] net: hns: Use phy_driver to setup Phy loopback Lin Yun Sheng
2017-06-29 18:14 ` [PATCH NET V7 0/2] Add loopback support in phy_driver and hns ethtool fix David Miller
2017-06-29 18:22 ` Andrew Lunn
2017-06-29 20:08 ` David Miller
2017-06-30 6:15 ` 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=d1d49cc5-b003-baeb-7607-303b930c536f@huawei.com \
--to=linyunsheng@huawei.com \
--cc=Yisen.Zhuang@huawei.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=gabriele.paoloni@huawei.com \
--cc=huangdaode@hisilicon.com \
--cc=john.garry@huawei.com \
--cc=liguozhu@hisilicon.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.com \
--cc=tremyfr@gmail.com \
--cc=xuwei5@hisilicon.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®