From: Jakub Kicinski <kuba@kernel.org>
To: Chris Packham <chris.packham@alliedtelesis.co.nz>
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
tsbogend@alpha.franken.de, andrew@lunn.ch, hkallweit1@gmail.com,
linux@armlinux.org.uk, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, sander@svanheule.net,
markus.stockhausen@gmx.de, devicetree@vger.kernel.org,
linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net-next v8 0/2] RTL9300 MDIO driver
Date: Mon, 3 Mar 2025 17:32:01 -0800 [thread overview]
Message-ID: <20250303173201.4205ed0c@kernel.org> (raw)
In-Reply-To: <20250227213248.2010986-1-chris.packham@alliedtelesis.co.nz>
On Fri, 28 Feb 2025 10:32:46 +1300 Chris Packham wrote:
> This series adds a driver for the MDIO controller on the RTL9300 family
> of devices. The controller is a little unique in that we can't access the SMI
> interfaces directly. This means we need to use the hardware description from
> the DTS to compute a mapping of switch port to mdio bus/address.
>
> The dt-bindings have been applied to net-next.
>
> I've dropped a patch that added PHYs to the cameo-rtl9302c board as I know that
> will need updating once some of the other in-flight changes make it into
> linux-mips.
Is the second patch going via the mips tree?
If so could you repost just patch 1 for net-next?
The second patch applies to net-next but with some fuzz,
I suspect that may be why we're not getting any reviews here.
--
pw-bot: cr
prev parent reply other threads:[~2025-03-04 1:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-27 21:32 [PATCH net-next v8 0/2] RTL9300 MDIO driver Chris Packham
2025-02-27 21:32 ` [PATCH net-next v8 1/2] net: mdio: Add " Chris Packham
2025-02-27 21:32 ` [PATCH net-next v8 2/2] mips: dts: realtek: Add MDIO controller Chris Packham
2025-03-04 1:32 ` Jakub Kicinski [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=20250303173201.4205ed0c@kernel.org \
--to=kuba@kernel.org \
--cc=andrew@lunn.ch \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=markus.stockhausen@gmx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=sander@svanheule.net \
--cc=tsbogend@alpha.franken.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.