The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Quentin Schulz <quentin.schulz@cherry.de>
To: John Clark <inindev@gmail.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>
Cc: Jonas Karlman <jonas@kwiboo.se>,
	Nicolas Frattaroli <nicolas.frattaroli@collabora.com>,
	Andrew Lunn <andrew@lunn.ch>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH RESEND v4 2/3] dt-bindings: arm: rockchip: Add Luckfox Omni3576 and Core3576 bindings
Date: Mon, 12 May 2025 10:27:32 +0200	[thread overview]
Message-ID: <9e96bec3-83c7-45b6-b2f7-0ccfe347643e@cherry.de> (raw)
In-Reply-To: <20250509122637.26674-3-inindev@gmail.com>

Hi John,

On 5/9/25 2:26 PM, John Clark wrote:
> This patch adds device tree binding support for Luckfox Core3576 Module
> based boards, specifically the Luckfox Omni3576, with compatibility for the
> Rockchip RK3576 SoC.
> 

Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>

Thanks!
Quentin

  reply	other threads:[~2025-05-12  8:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09 12:26 [PATCH RESEND v4 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576 John Clark
2025-05-09 12:26 ` [PATCH RESEND v4 1/3] dt-bindings: vendor-prefixes: Add luckfox prefix John Clark
2025-05-12  8:12   ` Quentin Schulz
2025-05-12  9:25     ` Conor Dooley
2025-05-09 12:26 ` [PATCH RESEND v4 2/3] dt-bindings: arm: rockchip: Add Luckfox Omni3576 and Core3576 bindings John Clark
2025-05-12  8:27   ` Quentin Schulz [this message]
2025-05-14 20:01   ` Rob Herring (Arm)
2025-05-09 12:26 ` [PATCH RESEND v4 3/3] arm64: dts: rockchip: Add Luckfox Omni3576 Board support John Clark
2025-05-12  8:25   ` Quentin Schulz

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=9e96bec3-83c7-45b6-b2f7-0ccfe347643e@cherry.de \
    --to=quentin.schulz@cherry.de \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=inindev@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=nicolas.frattaroli@collabora.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