From: Jakub Kicinski <kuba@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
kernel@pengutronix.de, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v5 1/3] ethtool: Add new result codes for TDR diagnostics
Date: Fri, 16 Aug 2024 10:19:19 -0700 [thread overview]
Message-ID: <20240816101919.785f6e9a@kernel.org> (raw)
In-Reply-To: <20240812073046.1728288-1-o.rempel@pengutronix.de>
On Mon, 12 Aug 2024 09:30:44 +0200 Oleksij Rempel wrote:
> Add new result codes to support TDR diagnostics in preparation for
> Open Alliance 1000BaseT1 TDR support:
>
> - ETHTOOL_A_CABLE_RESULT_CODE_NOISE: TDR not possible due to high noise
> level.
> - ETHTOOL_A_CABLE_RESULT_CODE_RESOLUTION_NOT_POSSIBLE: TDR resolution not
> possible / out of distance.
Oleksij, please improve your postings. You have no cover letter here.
No link to previous postings. You didn't take Andrew's review tags
from v4.
next prev parent reply other threads:[~2024-08-16 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-12 7:30 [PATCH net-next v5 1/3] ethtool: Add new result codes for TDR diagnostics Oleksij Rempel
2024-08-12 7:30 ` [PATCH net-next v5 2/3] phy: Add Open Alliance helpers for the PHY framework Oleksij Rempel
2024-08-12 7:30 ` [PATCH net-next v5 3/3] net: phy: dp83tg720: Add cable testing support Oleksij Rempel
2024-08-16 17:19 ` Jakub Kicinski [this message]
2024-08-16 17:20 ` [PATCH net-next v5 1/3] ethtool: Add new result codes for TDR diagnostics patchwork-bot+netdevbpf
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=20240816101919.785f6e9a@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=pabeni@redhat.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).