From: patchwork-bot+netdevbpf@kernel.org
To: James Hilliard <james.hilliard1@gmail.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, arnd@arndb.de,
jedrzej.jagielski@intel.com, andre.przywara@arm.com,
wens@kernel.org, jernej.skrabec@gmail.com,
maxime.chevallier@bootlin.com, linux-sunxi@lists.linux.dev,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
krzysztof.kozlowski@oss.qualcomm.com
Subject: Re: [PATCH net-next v11 0/2] net: phy: add X-Powers AC200/AC300 EPHY support
Date: Tue, 15 Sep 2026 01:50:08 +0000 [thread overview]
Message-ID: <178943700837.1306524.13969208982154394192.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260909-submit-acx00-of-dynamic-v1-v11-0-eb45e89ef918@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Wed, 09 Sep 2026 18:15:36 -0600 you wrote:
> This submission contains only the networking binding and PHY driver and
> is intended for net-next. The AC200 I2C register provider was submitted
> separately for the MFD tree:
>
> https://patch.msgid.link/20260907-submit-ac200-mfd-v11-0-58dd9dc7f69a@gmail.com
>
> The two series can build and be merged independently. AC300 needs only the
> networking series. The AC200 runtime path additionally needs the separately
> submitted MFD provider and binding. Their shared design point is the DT
> representation: the MDIO PHY-package node references the AC200 I2C node for
> access to package-control registers.
>
> [...]
Here is the summary with links:
- [net-next,v11,1/2] dt-bindings: net: x-powers: add AC200/AC300 EPHY packages
https://git.kernel.org/netdev/net-next/c/783f6f1fdcd5
- [net-next,v11,2/2] net: phy: add X-Powers AC200/AC300 EPHY driver
https://git.kernel.org/netdev/net-next/c/6cc2fbceb49b
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-09-15 1:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-10 0:15 [PATCH net-next v11 0/2] net: phy: add X-Powers AC200/AC300 EPHY support James Hilliard
2026-09-10 0:15 ` [PATCH net-next v11 1/2] dt-bindings: net: x-powers: add AC200/AC300 EPHY packages James Hilliard
2026-09-10 0:15 ` [PATCH net-next v11 2/2] net: phy: add X-Powers AC200/AC300 EPHY driver James Hilliard
2026-09-15 1:50 ` patchwork-bot+netdevbpf [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=178943700837.1306524.13969208982154394192.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andre.przywara@arm.com \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=james.hilliard1@gmail.com \
--cc=jedrzej.jagielski@intel.com \
--cc=jernej.skrabec@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=krzysztof.kozlowski@oss.qualcomm.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=linux@armlinux.org.uk \
--cc=maxime.chevallier@bootlin.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh@kernel.org \
--cc=wens@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.