From: Conor Dooley <conor@kernel.org>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: mkl@pengutronix.de, kernel@pengutronix.de,
mailhol.vincent@wanadoo.fr, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, heiko@sntech.de, cl@rock-chips.com,
linux-can@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v9 1/3] dt-bindings: can: rockchip_canfd: add rk3576 CAN controller
Date: Thu, 13 Nov 2025 19:40:04 +0000 [thread overview]
Message-ID: <20251113-bullfrog-destiny-977deea729e1@spud> (raw)
In-Reply-To: <20251113075419.482940-2-zhangqing@rock-chips.com>
[-- Attachment #1: Type: text/plain, Size: 241 bytes --]
On Thu, Nov 13, 2025 at 03:54:17PM +0800, Elaine Zhang wrote:
> Add documentation for the rockchip rk3576 CAN controller.
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-11-13 19:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 7:54 [PATCH v9 0/3] rockchip: add can for RK3576 Soc Elaine Zhang
2025-11-13 7:54 ` [PATCH v9 1/3] dt-bindings: can: rockchip_canfd: add rk3576 CAN controller Elaine Zhang
2025-11-13 19:40 ` Conor Dooley [this message]
2025-11-13 7:54 ` [PATCH v9 2/3] net: can: rockchip: Refactor the rkcanfd_devtype_data structure Elaine Zhang
2025-11-13 7:54 ` [PATCH v9 3/3] net: can: rockchip: add can for RK3576 Soc Elaine Zhang
2025-11-13 14:14 ` Marc Kleine-Budde
2025-11-14 9:55 ` zhangqing
2025-11-14 11:01 ` Marc Kleine-Budde
2025-11-14 12:14 ` zhangqing
2025-11-14 13:22 ` Marc Kleine-Budde
2025-11-14 13:28 ` 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=20251113-bullfrog-destiny-977deea729e1@spud \
--to=conor@kernel.org \
--cc=cl@rock-chips.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=mkl@pengutronix.de \
--cc=robh@kernel.org \
--cc=zhangqing@rock-chips.com \
/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