From: David Miller <davem@davemloft.net>
To: michael@walle.cc
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
linux@armlinux.org.uk
Subject: Re: [PATCH net-next 0/4] net: phy: broadcom: cable tester support
Date: Wed, 13 May 2020 12:52:55 -0700 (PDT) [thread overview]
Message-ID: <20200513.125255.2269307540440959207.davem@davemloft.net> (raw)
In-Reply-To: <20200513163524.31256-1-michael@walle.cc>
From: Michael Walle <michael@walle.cc>
Date: Wed, 13 May 2020 18:35:20 +0200
> Add cable tester support for the Broadcom PHYs. Support for it was
> developed on a BCM54140 Quad PHY which RDB register access.
>
> If there is a link partner the results are not as good as with an open
> cable. I guess we could retry if the measurement until all pairs had at
> least one valid result.
>
> changes since v1:
> - added Reviewed-by: tags
> - removed "div by 2" for cross shorts, just mention it in the commit
> message. The results are inconclusive if the tests are repeated. So
> just report the length as is for now.
> - fixed typo in commit message
Series applied, thanks.
next prev parent reply other threads:[~2020-05-13 19:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-13 16:35 Michael Walle
2020-05-13 16:35 ` [PATCH net-next v2 1/4] net: phy: broadcom: add exp register access methods without buslock Michael Walle
2020-05-13 16:35 ` [PATCH net-next v2 2/4] net: phy: broadcom: add bcm_phy_modify_exp() Michael Walle
2020-05-13 16:35 ` [PATCH net-next v2 3/4] net: phy: broadcom: add cable test support Michael Walle
2020-05-13 16:35 ` [PATCH net-next v2 4/4] net: phy: bcm54140: add cable diagnostics support Michael Walle
2020-05-13 19:52 ` David Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-05-09 22:37 [PATCH net-next 0/4] net: phy: broadcom: cable tester support Michael Walle
2020-05-10 18:21 ` Jakub Kicinski
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=20200513.125255.2269307540440959207.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--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
all inboxes | Powered by JetHome®