From: David Miller <davem@davemloft.net>
To: o.rempel@pengutronix.de
Cc: andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com,
kuba@kernel.org, corbet@lwn.net, mkubecek@suse.cz,
david@protonic.nl, kernel@pengutronix.de,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
linux@armlinux.org.uk, mkl@pengutronix.de, marex@denx.de,
christian.herber@nxp.com
Subject: Re: [PATCH net-next v3 0/2] provide KAPI for SQI
Date: Thu, 21 May 2020 17:18:15 -0700 (PDT) [thread overview]
Message-ID: <20200521.171815.1268044117965833956.davem@davemloft.net> (raw)
In-Reply-To: <20200520062915.29493-1-o.rempel@pengutronix.de>
From: Oleksij Rempel <o.rempel@pengutronix.de>
Date: Wed, 20 May 2020 08:29:13 +0200
> This patches are extending ethtool netlink interface to export Signal
> Quality Index (SQI). SQI provided by 100Base-T1 PHYs and can be used for
> cable diagnostic. Compared to a typical cable tests, this value can be
> only used after link is established.
>
> changes v3:
> - rename __ethtool_get_sqi* to linkstate_get_sqi*. And move this
> functions to the net/ethtool/linkstate.c
> - protect linkstate_get_sqi* with locking
>
> changes v2:
> - use u32 instead of u8 for SQI
> - add SQI_MAX field and callbacks
> - some style fixes in the rst.
> - do not convert index to shifted index.
Series applied, thank you.
prev parent reply other threads:[~2020-05-22 0:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 6:29 [PATCH net-next v3 0/2] provide KAPI for SQI Oleksij Rempel
2020-05-20 6:29 ` [PATCH net-next v3 1/2] ethtool: provide UAPI for PHY Signal Quality Index (SQI) Oleksij Rempel
2020-05-20 14:29 ` Andrew Lunn
2020-05-20 14:45 ` Michal Kubecek
2020-05-20 15:07 ` Oleksij Rempel
2020-05-20 15:23 ` Michal Kubecek
2020-05-20 15:30 ` Andrew Lunn
2020-05-20 17:39 ` Oleksij Rempel
2020-05-20 6:29 ` [PATCH net-next v3 2/2] net: phy: tja11xx: add SQI support Oleksij Rempel
2020-05-20 14:29 ` Andrew Lunn
2020-05-22 0:18 ` David Miller [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=20200521.171815.1268044117965833956.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=andrew@lunn.ch \
--cc=christian.herber@nxp.com \
--cc=corbet@lwn.net \
--cc=david@protonic.nl \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marex@denx.de \
--cc=mkl@pengutronix.de \
--cc=mkubecek@suse.cz \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
/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).