From: patchwork-bot+netdevbpf@kernel.org
To: =?utf-8?q?J=2E_Neusch=C3=A4fer_via_B4_Relay_=3Cdevnull+j=2Ene=2Eposteo=2Enet?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org,
=?utf-8?q?=40kernel=2Eorg=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org
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, claudiu.manoil@nxp.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, j.ne@posteo.net
Subject: Re: [PATCH v2 0/3] net: Convert Gianfar (Triple Speed Ethernet Controller) bindings to YAML
Date: Wed, 05 Mar 2025 01:20:37 +0000 [thread overview]
Message-ID: <174113763773.356990.16443776503702976199.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20250228-gianfar-yaml-v2-0-6beeefbd4818@posteo.net>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 28 Feb 2025 18:32:49 +0100 you wrote:
> The aim of this series is to modernize the device tree bindings for the
> Freescale "Gianfar" ethernet controller (a.k.a. TSEC, Triple Speed
> Ethernet Controller) by converting them to YAML.
>
> Signed-off-by: J. Neuschäfer <j.ne@posteo.net>
> ---
> Changes in v2:
> - various cleanups suggested by reviewers
> - use a 'select:' schema to disambiguate compatible = "gianfar" between
> network controller and MDIO nodes
> - Link to v1: https://lore.kernel.org/r/20250220-gianfar-yaml-v1-0-0ba97fd1ef92@posteo.net
>
> [...]
Here is the summary with links:
- [v2,1/3] dt-bindings: net: Convert fsl,gianfar-{mdio,tbi} to YAML
https://git.kernel.org/netdev/net-next/c/e4c4522390c9
- [v2,2/3] dt-bindings: net: fsl,gianfar-mdio: Update information about TBI
https://git.kernel.org/netdev/net-next/c/0386e29e60bd
- [v2,3/3] dt-bindings: net: Convert fsl,gianfar to YAML
https://git.kernel.org/netdev/net-next/c/a70fdd936818
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:[~2025-03-05 1:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-28 17:32 [PATCH v2 0/3] net: Convert Gianfar (Triple Speed Ethernet Controller) bindings to YAML J. Neuschäfer via B4 Relay
2025-02-28 17:32 ` [PATCH v2 1/3] dt-bindings: net: Convert fsl,gianfar-{mdio,tbi} " J. Neuschäfer via B4 Relay
2025-02-28 22:02 ` Rob Herring (Arm)
2025-02-28 17:32 ` [PATCH v2 2/3] dt-bindings: net: fsl,gianfar-mdio: Update information about TBI J. Neuschäfer via B4 Relay
2025-02-28 17:32 ` [PATCH v2 3/3] dt-bindings: net: Convert fsl,gianfar to YAML J. Neuschäfer via B4 Relay
2025-02-28 22:08 ` Rob Herring (Arm)
2025-03-05 1:20 ` 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=174113763773.356990.16443776503702976199.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc==?utf-8?q?=40kernel=2Eorg=3E?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc==?utf-8?q?J=2E_Neusch=C3=A4fer_via_B4_Relay_=3Cdevnull+j=2Ene=2Eposteo=2Enet?=@aws-us-west-2-korg-oddjob-rhel9-1.codeaurora.org \
--cc=andrew+netdev@lunn.ch \
--cc=claudiu.manoil@nxp.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=j.ne@posteo.net \
--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 \
/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;
as well as URLs for NNTP newsgroup(s).