From: patchwork-bot+netdevbpf@kernel.org
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
linux-can@vger.kernel.org, kernel@pengutronix.de,
quchaosheng000406@163.com, robh@kernel.org
Subject: Re: [PATCH net-next 1/7] dt-bindings: net: can: ifi,canfd-1.0: Convert to DT schema
Date: Tue, 17 Nov 2026 00:20:12 +0000 [thread overview]
Message-ID: <179487481277.257811.5528472784391485936.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20261113071325.4092169-2-mkl@pengutronix.de>
Hello:
This series was applied to netdev/net-next.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Fri, 13 Nov 2026 08:08:49 +0100 you wrote:
> From: Quchaosheng <quchaosheng000406@163.com>
>
> Convert the IFI CAN-FD controller binding from free-form text to DT
> schema.
>
> Reference can-controller.yaml. interrupts is required: the driver obtains
> it with platform_get_irq().
>
> [...]
Here is the summary with links:
- [net-next,1/7] dt-bindings: net: can: ifi,canfd-1.0: Convert to DT schema
https://git.kernel.org/netdev/net-next/c/0efc358417de
- [net-next,2/7] dt-bindings: net: can: bosch,cc770: Convert to DT schema
https://git.kernel.org/netdev/net-next/c/489a164909b2
- [net-next,3/7] dt-bindings: net: can: holt,hi311x: Convert to DT schema
https://git.kernel.org/netdev/net-next/c/f0d13562fbdb
- [net-next,4/7] net: can: cc770: update the binding file reference in the driver comment
https://git.kernel.org/netdev/net-next/c/8c4de4078890
- [net-next,5/7] dt-bindings: net: can: fsl,mpc5xxx-mscan: Convert to DT schema
https://git.kernel.org/netdev/net-next/c/1911b1c42960
- [net-next,6/7] dt-bindings: net: can: convert grcan to DT schema
https://git.kernel.org/netdev/net-next/c/ea1907f738d0
- [net-next,7/7] net: can: grcan: update the binding file reference in the driver comment
https://git.kernel.org/netdev/net-next/c/194bf22b60a5
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:[~2026-11-17 0:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 7:08 [PATCH net-next 0/7] pull-request: can-next 2026-11-13 Marc Kleine-Budde
2026-11-13 7:08 ` [PATCH net-next 1/7] dt-bindings: net: can: ifi,canfd-1.0: Convert to DT schema Marc Kleine-Budde
2026-11-17 0:20 ` patchwork-bot+netdevbpf [this message]
2026-11-13 7:08 ` [PATCH net-next 2/7] dt-bindings: net: can: bosch,cc770: " Marc Kleine-Budde
2026-11-13 7:08 ` [PATCH net-next 3/7] dt-bindings: net: can: holt,hi311x: " Marc Kleine-Budde
2026-11-13 7:08 ` [PATCH net-next 4/7] net: can: cc770: update the binding file reference in the driver comment Marc Kleine-Budde
2026-11-13 7:08 ` [PATCH net-next 5/7] dt-bindings: net: can: fsl,mpc5xxx-mscan: Convert to DT schema Marc Kleine-Budde
2026-11-13 7:08 ` [PATCH net-next 6/7] dt-bindings: net: can: convert grcan " Marc Kleine-Budde
2026-11-13 7:08 ` [PATCH net-next 7/7] net: can: grcan: update the binding file reference in the driver comment Marc Kleine-Budde
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=179487481277.257811.5528472784391485936.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.kernel.org \
--cc=quchaosheng000406@163.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