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,
jernej.skrabec@gmail.com
Subject: Re: [PATCH net-next] Revert "riscv: dts: allwinner: d1: Add CAN controller nodes"
Date: Mon, 07 Aug 2023 19:30:24 +0000 [thread overview]
Message-ID: <169143662467.21933.9656894159328024751.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807074222.1576119-2-mkl@pengutronix.de>
Hello:
This patch was applied to netdev/net-next.git (main)
by Marc Kleine-Budde <mkl@pengutronix.de>:
On Mon, 7 Aug 2023 09:42:22 +0200 you wrote:
> It turned out the dtsi changes were not quite ready, revert them for
> now.
>
> This reverts commit 6ea1ad888f5900953a21853e709fa499fdfcb317.
>
> Link: https://lore.kernel.org/all/2690764.mvXUDI8C0e@jernej-laptop
> Suggested-by: Jernej Škrabec <jernej.skrabec@gmail.com>
> Link: https://lore.kernel.org/all/20230807-riscv-allwinner-d1-revert-can-controller-nodes-v1-1-eb3f70b435d9@pengutronix.de
> Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
>
> [...]
Here is the summary with links:
- [net-next] Revert "riscv: dts: allwinner: d1: Add CAN controller nodes"
https://git.kernel.org/netdev/net-next/c/84059a0ef5c6
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:[~2023-08-07 19:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 7:42 [PATCH net-next 0/1] pull-request: can-next 2023-08-07 Marc Kleine-Budde
2023-08-07 7:42 ` [PATCH net-next] Revert "riscv: dts: allwinner: d1: Add CAN controller nodes" Marc Kleine-Budde
2023-08-07 7:48 ` Jernej Škrabec
2023-08-07 19: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=169143662467.21933.9656894159328024751.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=davem@davemloft.net \
--cc=jernej.skrabec@gmail.com \
--cc=kernel@pengutronix.de \
--cc=kuba@kernel.org \
--cc=linux-can@vger.kernel.org \
--cc=mkl@pengutronix.de \
--cc=netdev@vger.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 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.