From: patchwork-bot+netdevbpf@kernel.org
To: Rob Herring (Arm) <robh@kernel.org>
Cc: andrew@lunn.ch, hkallweit1@gmail.com, linux@armlinux.org.uk,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, krzk+dt@kernel.org, conor+dt@kernel.org,
f.fainelli@gmail.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] dt-bindings: net: Document Marvell PHY "marvell,reg-init"
Date: Tue, 29 Sep 2026 13:40:04 +0000 [thread overview]
Message-ID: <179068920477.499886.7765098308090780427.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260925140410.1157036-2-robh@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Paolo Abeni <pabeni@redhat.com>:
On Fri, 25 Sep 2026 09:04:10 -0500 you wrote:
> The Marvell PHY driver consumes marvell,reg-init as one or more
> <page register mask value> tuples. Define the property so dtbs_check
> validates the existing board descriptions.
>
> Existing users have no compatible or just "ethernet-phy-ieee802.3-c22"
> so this has to go into the generic ethernet-phy.yaml schema. Marking it
> deprecated both for that reason and because opaque register
> initialization values are discouraged in DT.
>
> [...]
Here is the summary with links:
- [net-next,v2] dt-bindings: net: Document Marvell PHY "marvell,reg-init"
https://git.kernel.org/netdev/net-next/c/63f028c4dd73
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-29 13:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-25 14:04 Rob Herring (Arm)
2026-09-25 14:46 ` Andrew Lunn
2026-09-29 13:40 ` 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=179068920477.499886.7765098308090780427.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®