public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: John Clark <inindev@gmail.com>
Cc: heiko@sntech.de, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
	robh@kernel.org, krzysztof.kozlowski@linaro.org,
	conor+dt@kernel.org, jonas@kwiboo.se,
	frattaroli.nicolas@gmail.com, andrew@lunn.ch
Subject: Re: [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add luckfox prefix
Date: Tue, 6 May 2025 16:45:23 +0100	[thread overview]
Message-ID: <20250506-snitch-entitle-25cbf145619a@spud> (raw)
In-Reply-To: <20250506114115.613616-2-inindev@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 239 bytes --]

On Tue, May 06, 2025 at 07:41:13AM -0400, John Clark wrote:
> Add vendor prefix for Shenzhen Luckfox Technology Co., Ltd., which
> produces development boards like the Luckfox Omni3576.

Acked-by: Conor Dooley <conor.dooley@microchip.com>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-05-06 15:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 11:41 [PATCH v3 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576 John Clark
2025-05-06 11:41 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: Add luckfox prefix John Clark
2025-05-06 15:45   ` Conor Dooley [this message]
2025-05-06 11:41 ` [PATCH v3 2/3] dt-bindings: arm: rockchip: Add Luckfox Omni3576 and Core3576 bindings John Clark
2025-05-06 15:44   ` Conor Dooley
2025-05-06 15:54     ` John Clark
2025-05-06 16:34       ` Conor Dooley
2025-05-06 16:38       ` Heiko Stübner
2025-05-06 11:41 ` [PATCH v3 3/3] arm64: dts: rockchip: Add Luckfox Omni3576 Board support John Clark
2025-05-06 17:05 ` [PATCH v3 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576 Krzysztof Kozlowski
2025-05-06 17:14   ` John Clark
2025-05-06 17:16     ` Krzysztof Kozlowski
2025-05-06 18:23 ` Rob Herring (Arm)
2025-05-06 21:18   ` Heiko Stübner

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=20250506-snitch-entitle-25cbf145619a@spud \
    --to=conor@kernel.org \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frattaroli.nicolas@gmail.com \
    --cc=heiko@sntech.de \
    --cc=inindev@gmail.com \
    --cc=jonas@kwiboo.se \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.org \
    --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