From: patchwork-bot+netdevbpf@kernel.org
To: chunzhi.lin <linchunzhi0@gmail.com>
Cc: netdev@vger.kernel.org, Frank.Sae@motor-comm.com, andrew@lunn.ch,
hkallweit1@gmail.com, linux@armlinux.org.uk, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, davem@davemloft.net,
linux-acpi@vger.kernel.org, rafael@kernel.org, lenb@kernel.org
Subject: Re: [PATCH net-next v2 0/2] net: phy: motorcomm: add ACPI _DSD property support
Date: Tue, 12 May 2026 01:19:53 +0000 [thread overview]
Message-ID: <177854879356.2528168.9082191580005110678.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260507040221.3679454-1-linchunzhi0@gmail.com>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Thu, 7 May 2026 12:02:19 +0800 you wrote:
> Hi,
>
> This series makes the Motorcomm PHY driver parse firmware properties via
> device_property_*() so the same property set can be provided by either
> Devicetree or ACPI _DSD.
>
> Patch 1 switches drivers/net/phy/motorcomm.c from of_property_*() to
> device_property_*() on &phydev->mdio.dev.
>
> [...]
Here is the summary with links:
- [v2,1/2] net: phy: motorcomm: use device properties for firmware tuning
https://git.kernel.org/netdev/net-next/c/fffedfece2b4
- [v2,2/2] docs: acpi: dsd: add Motorcomm yt8xxx PHY properties
https://git.kernel.org/netdev/net-next/c/28f431eac1e5
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-05-12 1:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 4:02 [PATCH net-next v2 0/2] net: phy: motorcomm: add ACPI _DSD property support chunzhi.lin
2026-05-07 4:02 ` [PATCH v2 1/2] net: phy: motorcomm: use device properties for firmware tuning chunzhi.lin
2026-05-07 4:02 ` [PATCH v2 2/2] docs: acpi: dsd: add Motorcomm yt8xxx PHY properties chunzhi.lin
2026-05-12 1:19 ` 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=177854879356.2528168.9082191580005110678.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Sae@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=lenb@kernel.org \
--cc=linchunzhi0@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox