From: patchwork-bot+linux-riscv@kernel.org
To: John Watts <contact@jookia.org>
Cc: linux-riscv@lists.infradead.org, linux-sunxi@lists.linux.dev,
devicetree@vger.kernel.org, conor+dt@kernel.org,
aou@eecs.berkeley.edu, samuel@sholland.org,
linux-kernel@vger.kernel.org, jernej.skrabec@gmail.com,
wens@csie.org, robh+dt@kernel.org, palmer@dabbelt.com,
krzysztof.kozlowski+dt@linaro.org, paul.walmsley@sifive.com,
bigunclemax@gmail.com, mkl@pengutronix.de,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3] riscv: dts: allwinner: d1: Add CAN controller nodes
Date: Fri, 01 Sep 2023 16:25:15 +0000 [thread overview]
Message-ID: <169358551557.8276.8875001900828239804.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230807191952.2019208-1-contact@jookia.org>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Chen-Yu Tsai <wens@csie.org>:
On Tue, 8 Aug 2023 05:19:52 +1000 you wrote:
> The Allwinner D1, T113 provide two CAN controllers that are variants
> of the R40 controller.
>
> I have tested support for these controllers on two boards:
>
> - A Lichee Panel RV 86 Panel running a D1 chip
> - A Mango Pi MQ Dual running a T113-s3 chip
>
> [...]
Here is the summary with links:
- [v3] riscv: dts: allwinner: d1: Add CAN controller nodes
https://git.kernel.org/riscv/c/f05af44f6913
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-09-01 16:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 19:19 [PATCH v3] riscv: dts: allwinner: d1: Add CAN controller nodes John Watts
[not found] ` <49ce2d9c-eb38-4ceb-bae1-0409df876e9b@web.de>
2023-08-08 14:32 ` Conor Dooley
2023-08-08 14:36 ` Marc Kleine-Budde
2023-08-13 4:17 ` Chen-Yu Tsai
2023-08-13 4:23 ` John Watts
2023-08-13 6:14 ` Chen-Yu Tsai
2023-08-13 6:16 ` John Watts
2023-09-01 16:25 ` patchwork-bot+linux-riscv [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=169358551557.8276.8875001900828239804.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bigunclemax@gmail.com \
--cc=conor+dt@kernel.org \
--cc=contact@jookia.org \
--cc=devicetree@vger.kernel.org \
--cc=jernej.skrabec@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=mkl@pengutronix.de \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=wens@csie.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