netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Christian Marangi <ansuelsmth@gmail.com>
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>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH v3 1/4] net: phy: at803x: generalize cdt fault length function
Date: Thu, 4 Jan 2024 13:07:38 +0000	[thread overview]
Message-ID: <20240104130738.GH31813@kernel.org> (raw)
In-Reply-To: <20240103124637.3078-2-ansuelsmth@gmail.com>

On Wed, Jan 03, 2024 at 01:46:32PM +0100, Christian Marangi wrote:
> Generalize cable test fault length function since they all base on the
> same magic values (already reverse engineered to understand the meaning
> of it) to have consistenct values on every PHY.
> 
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>

Reviewed-by: Simon Horman <horms@kernel.org>

  reply	other threads:[~2024-01-04 13:07 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03 12:46 [net-next PATCH v3 0/4] net: phy: at803x: even more generalization Christian Marangi
2024-01-03 12:46 ` [net-next PATCH v3 1/4] net: phy: at803x: generalize cdt fault length function Christian Marangi
2024-01-04 13:07   ` Simon Horman [this message]
2024-01-03 12:46 ` [net-next PATCH v3 2/4] net: phy: at803x: refactor qca808x cable test get status function Christian Marangi
2024-01-04 13:03   ` Simon Horman
2024-01-04 13:15     ` Christian Marangi
2024-01-03 12:46 ` [net-next PATCH v3 3/4] net: phy: at803x: add support for cdt cross short test for qca808x Christian Marangi
2024-01-03 12:46 ` [net-next PATCH v3 4/4] net: phy: at803x: make read_status more generic Christian Marangi

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=20240104130738.GH31813@kernel.org \
    --to=horms@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=ansuelsmth@gmail.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --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).