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 v4 4/4] net: phy: at803x: make read_status more generic
Date: Fri, 5 Jan 2024 18:28:34 +0000 [thread overview]
Message-ID: <20240105182834.GY31813@kernel.org> (raw)
In-Reply-To: <20240104213044.4653-5-ansuelsmth@gmail.com>
On Thu, Jan 04, 2024 at 10:30:41PM +0100, Christian Marangi wrote:
> Make read_status more generic in preparation on moving it to shared
> library as other PHY Family Driver will have the exact same
> implementation.
>
> The only specific part was a check for AR8031/33 if 1000basex was used.
> The check is moved to a dedicated function specific for those PHYs.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-01-05 18:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-04 21:30 [net-next PATCH v4 0/4] net: phy: at803x: even more generalization Christian Marangi
2024-01-04 21:30 ` [net-next PATCH v4 1/4] net: phy: at803x: generalize cdt fault length function Christian Marangi
2024-01-04 21:30 ` [net-next PATCH v4 2/4] net: phy: at803x: refactor qca808x cable test get status function Christian Marangi
2024-01-05 18:26 ` Simon Horman
2024-01-04 21:30 ` [net-next PATCH v4 3/4] net: phy: at803x: add support for cdt cross short test for qca808x Christian Marangi
2024-01-05 18:27 ` Simon Horman
2024-01-04 21:30 ` [net-next PATCH v4 4/4] net: phy: at803x: make read_status more generic Christian Marangi
2024-01-05 18:28 ` Simon Horman [this message]
2024-01-07 16:30 ` [net-next PATCH v4 0/4] net: phy: at803x: even more generalization 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=20240105182834.GY31813@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).