From: patchwork-bot+netdevbpf@kernel.org
To: Frank Li <Frank.Li@nxp.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, vz@mleia.com
Subject: Re: [PATCH v2 1/1] dt-bindings: net: convert nxp,lpc1850-dwmac.txt to yaml format
Date: Wed, 02 Jul 2025 00:50:17 +0000 [thread overview]
Message-ID: <175141741724.160580.15489613753821420716.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250630161613.2838039-1-Frank.Li@nxp.com>
Hello:
This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Mon, 30 Jun 2025 12:16:12 -0400 you wrote:
> Convert nxp,lpc1850-dwmac.txt to yaml format.
>
> Additional changes:
> - compatible string add fallback as "nxp,lpc1850-dwmac", "snps,dwmac-3.611"
> "snps,dwmac".
> - add common interrupts, interrupt-names, clocks, clock-names, resets and
> reset-names properties.
> - add ref snps,dwmac.yaml.
> - add phy-mode in example to avoid dt_binding_check warning.
> - update examples to align lpc18xx.dtsi.
>
> [...]
Here is the summary with links:
- [v2,1/1] dt-bindings: net: convert nxp,lpc1850-dwmac.txt to yaml format
https://git.kernel.org/netdev/net-next/c/69fcb70c4334
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
next prev parent reply other threads:[~2025-07-02 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 16:16 [PATCH v2 1/1] dt-bindings: net: convert nxp,lpc1850-dwmac.txt to yaml format Frank Li
2025-07-02 0:50 ` patchwork-bot+netdevbpf [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-02 9:17 kernel test robot
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=175141741724.160580.15489613753821420716.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=imx@lists.linux.dev \
--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=robh@kernel.org \
--cc=vz@mleia.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 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.