From: patchwork-bot+netdevbpf@kernel.org
To: Rob Herring (Arm) <robh@kernel.org>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@kernel.org,
kuba@kernel.org, pabeni@redhat.com, krzk+dt@kernel.org,
conor+dt@kernel.org, richardcochran@gmail.com,
treding@nvidia.com, jonathanh@nvidia.com,
alexandre.torgue@foss.st.com, peppe.cavallaro@st.com,
joabreu@synopsys.com, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next v2] dt-bindings: net: Convert snps,dwc-qos-ethernet to DT schema
Date: Mon, 09 Nov 2026 23:30:26 +0000 [thread overview]
Message-ID: <179426702692.3543549.11224444718065652161.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261103220402.471214-2-robh@kernel.org>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 3 Nov 2026 16:04:01 -0600 you wrote:
> Convert the "snps,dwc-qos-ethernet-4.10" binding to DT schema format.
> The binding uses several common snps,dwmac properties, so move them to
> the snps,dwmac-common.yaml schema.
>
> Drop support for standalone "snps,dwc-qos-ethernet-4.10" compatible
> and "axis,artpec6-eqos" as there are no users. Also drop the
> "snps,dwc-qos-ethernet-mdio" as it is also unused. Add the interconnects
> and iommus properties. Replaced the example with one from Tegra186.
>
> [...]
Here is the summary with links:
- [net-next,v2] dt-bindings: net: Convert snps,dwc-qos-ethernet to DT schema
https://git.kernel.org/netdev/net-next/c/47d30748de0b
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-11-09 23:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-03 22:04 Rob Herring (Arm)
2026-11-09 23:30 ` 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=179426702692.3543549.11224444718065652161.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=alexandre.torgue@foss.st.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@kernel.org \
--cc=joabreu@synopsys.com \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--cc=richardcochran@gmail.com \
--cc=robh@kernel.org \
--cc=treding@nvidia.com \
/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®