From: Christian Marangi <ansuelsmth@gmail.com>
To: Jakub Kicinski <kuba@kernel.org>
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>,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [net-next PATCH v2 0/4] net: phy: at803x: even more generalization
Date: Tue, 2 Jan 2024 23:41:16 +0100 [thread overview]
Message-ID: <6594910c.df0a0220.d72d6.9947@mx.google.com> (raw)
In-Reply-To: <20240102143707.69f08d5a@kernel.org>
On Tue, Jan 02, 2024 at 02:37:07PM -0800, Jakub Kicinski wrote:
> On Tue, 2 Jan 2024 15:03:24 +0100 Christian Marangi wrote:
> > This is part 3 of at803x required patches to split the PHY driver
> > in more specific PHY Family driver.
> >
> > While adding support for a new PHY Family qca807x it was notice lots
> > of similarities with the qca808x cdt function. Hence this series
> > is done to make things easier in the future when qca807x PHY will be
> > submitted.
>
> Does not apply..
Yes sorry was based on a tool old net-next branch and notice the fail on
patchwork. Was waiting the 24 hours to resend rebased.
Sorry for the noise.
--
Ansuel
prev parent reply other threads:[~2024-01-02 22:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 14:03 [net-next PATCH v2 0/4] net: phy: at803x: even more generalization Christian Marangi
2024-01-02 14:03 ` [net-next PATCH v2 1/4] net: phy: at803x: generalize cdt fault length function Christian Marangi
2024-01-02 14:03 ` [net-next PATCH v2 2/4] net: phy: at803x: refactor qca808x cable test get status function Christian Marangi
2024-01-02 14:03 ` [net-next PATCH v2 3/4] net: phy: at803x: add support for cdt cross short test for qca808x Christian Marangi
2024-01-02 14:03 ` [net-next PATCH v2 4/4] net: phy: at803x: make read_status more generic Christian Marangi
2024-01-02 22:37 ` [net-next PATCH v2 0/4] net: phy: at803x: even more generalization Jakub Kicinski
2024-01-02 22:41 ` Christian Marangi [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=6594910c.df0a0220.d72d6.9947@mx.google.com \
--to=ansuelsmth@gmail.com \
--cc=andrew@lunn.ch \
--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