From: patchwork-bot+netdevbpf@kernel.org
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: eichest@gmail.com, 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-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] dt-bindings: net: micrel: Fix KSZ8041RNLI dtbs_check warnings
Date: Thu, 19 Mar 2026 00:44:28 +0000 [thread overview]
Message-ID: <177388106828.935482.9940657343984545762.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1773734298.git.geert+renesas@glider.be>
Hello:
This series was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Tue, 17 Mar 2026 09:02:44 +0100 you wrote:
> Hi all,
>
> "make dtbs_check" reports several warnings due to some KSZ8041RNLI PHY
> nodes having the "micrel,led-mode" property, while the DT bindings
> prohibit this.
>
> Apparently the DT bindings are incorrect, so this patch series fixes
> that, after a customary cleanup.
>
> [...]
Here is the summary with links:
- [v2,1/2] dt-bindings: net: micrel: Sort lists
https://git.kernel.org/netdev/net-next/c/46906242fe61
- [v2,2/2] dt-bindings: net: micrel: KSZ8041RNLI supports LED mode
https://git.kernel.org/netdev/net-next/c/22214fb2fad0
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-03-19 0:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 8:02 [PATCH v2 0/2] dt-bindings: net: micrel: Fix KSZ8041RNLI dtbs_check warnings Geert Uytterhoeven
2026-03-17 8:02 ` [PATCH v2 1/2] dt-bindings: net: micrel: Sort lists Geert Uytterhoeven
2026-03-17 8:02 ` [PATCH v2 2/2] dt-bindings: net: micrel: KSZ8041RNLI supports LED mode Geert Uytterhoeven
2026-03-19 0:44 ` 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=177388106828.935482.9940657343984545762.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=eichest@gmail.com \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@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