From: Jakub Kicinski <kuba@kernel.org>
To: Charles Perry <charles.perry@microchip.com>
Cc: <netdev@vger.kernel.org>, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v2 0/2] Add support for PIC64-HPSC/HX MDIO controller
Date: Thu, 26 Mar 2026 20:33:09 -0700 [thread overview]
Message-ID: <20260326203309.7154152d@kernel.org> (raw)
In-Reply-To: <20260323220254.3822444-1-charles.perry@microchip.com>
On Mon, 23 Mar 2026 15:02:52 -0700 Charles Perry wrote:
> .../net/microchip,pic64hpsc-mdio.yaml | 68 +++++++
> drivers/net/mdio/Kconfig | 7 +
> drivers/net/mdio/Makefile | 1 +
> drivers/net/mdio/mdio-pic64hpsc.c | 192 ++++++++++++++++++
Speaking under correction from PHY maintainers but I think we need
a MAINTAINERS entry that will cover Microchip MDIO, or at least the
files you're adding. Important read:
https://docs.kernel.org/next/maintainer/feature-and-driver-maintainers.html
--
pw-bot: cr
next prev parent reply other threads:[~2026-03-27 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-23 22:02 [PATCH net-next v2 0/2] Add support for PIC64-HPSC/HX MDIO controller Charles Perry
2026-03-23 22:02 ` [PATCH net-next v2 1/2] dt-bindings: net: document Microchip " Charles Perry
2026-04-07 17:00 ` Rob Herring
2026-04-07 18:01 ` Charles Perry
2026-03-23 22:02 ` [PATCH net-next v2 2/2] net: mdio: add a driver for " Charles Perry
2026-03-27 3:33 ` Jakub Kicinski [this message]
2026-03-27 12:34 ` [PATCH net-next v2 0/2] Add support " Charles Perry
2026-03-27 23:51 ` Jakub Kicinski
2026-03-30 13:59 ` Charles Perry
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=20260326203309.7154152d@kernel.org \
--to=kuba@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=charles.perry@microchip.com \
--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@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
/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.