From: Yunsheng Lin <linyunsheng@huawei.com>
To: Russell King - ARM Linux <linux@armlinux.org.uk>
Cc: Andrew Lunn <andrew@lunn.ch>,
Florian Fainelli <f.fainelli@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
Weiwei Deng <dengweiwei@huawei.com>,
"Yisen.Zhuang@huawei.com" <Yisen.Zhuang@huawei.com>,
"huangdaode@hisilicon.com" <huangdaode@hisilicon.com>,
"lipeng321@huawei.com" <lipeng321@huawei.com>,
"salil.mehta@huawei.com" <salil.mehta@huawei.com>,
lijianhua 00216010 <lijianhua@huawei.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: Question: pause mode disabled for marvell 88e151x phy
Date: Sat, 5 Jan 2019 11:28:19 +0800 [thread overview]
Message-ID: <6e8034d9-cd60-2846-ef33-f8a04069e1ee@huawei.com> (raw)
In-Reply-To: <20181217143633.GH26090@n2100.armlinux.org.uk>
On 2018/12/17 22:36, Russell King - ARM Linux wrote:
> I'll try to do further diagnosis over Christmas in case I've missed
> something, but I suspect it may be one of those "weird behaviour" issues
> where the safest action is to disable pause mode as per my commit -
> which is far saner than having mismatched pause status on either end
> of a link. However, given that Marvell specs are all NDA-only, it's
> very difficult to investigate beyond "this is the observed behaviour".
Hi,
Is there any update on the further diagnosis?
>
next prev parent reply other threads:[~2019-01-05 3:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-15 8:07 Question: pause mode disabled for marvell 88e151x phy Yunsheng Lin
2018-12-15 10:37 ` Russell King - ARM Linux
2018-12-17 9:42 ` Yunsheng Lin
2018-12-17 14:36 ` Russell King - ARM Linux
2018-12-18 9:34 ` Yunsheng Lin
2018-12-18 10:08 ` Russell King - ARM Linux
2019-01-05 3:28 ` Yunsheng Lin [this message]
2019-01-23 22:41 ` Russell King - ARM Linux admin
2019-01-24 12:28 ` Yunsheng Lin
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=6e8034d9-cd60-2846-ef33-f8a04069e1ee@huawei.com \
--to=linyunsheng@huawei.com \
--cc=Yisen.Zhuang@huawei.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=dengweiwei@huawei.com \
--cc=f.fainelli@gmail.com \
--cc=huangdaode@hisilicon.com \
--cc=lijianhua@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=lipeng321@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=salil.mehta@huawei.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