public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: John Clark <inindev@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>, heiko@sntech.de
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-rockchip@lists.infradead.org, robh@kernel.org,
	conor+dt@kernel.org, jonas@kwiboo.se,
	frattaroli.nicolas@gmail.com, andrew@lunn.ch
Subject: Re: [PATCH v3 0/3] Add Luckfox Omni3576 Carrier Board support for RK3576
Date: Tue, 6 May 2025 13:14:05 -0400	[thread overview]
Message-ID: <043117e7-9fd7-4ddc-8fd9-433c5b8c5dc6@gmail.com> (raw)
In-Reply-To: <bb857b7d-97f8-4505-9d2a-1ba9d6319710@linaro.org>

On 5/6/25 1:05 PM, Krzysztof Kozlowski wrote:
> On 06/05/2025 13:41, John Clark wrote:
>> This series adds device tree support for the Luckfox Omni3576
>> Carrier Board with the Core3576 Module, powered by the Rockchip
>> RK3576 SoC (four Cortex-A72 cores, four Cortex-A53 cores, Mali-G52
>> MC3 GPU). It enables essential functionality for booting Linux and
>> basic connectivity, with plans for future support of peripherals
>> like WiFi, MIPI-DSI, HDMI, and Ethernet.
>>
>> The series was first posted as v1 at:
>> https://lore.kernel.org/linux-rockchip/20250502205533.51744-1-inindev@gmail.com
>> v2 at:
>> https://lore.kernel.org/linux-rockchip/20250504102447.153551-1-inindev@gmail.com
> You got extensive guideline what to do in my reply to avoid exactly the
> mistake you did ... yet you ignored the guideline.

I did not ignore it, I took this to mean:

 > Do not attach (thread) your patchsets to some other threads (unrelated
 > or older versions). This buries them deep in the mailbox and might
 > interfere with applying entire sets."

that I should not use the "--in-reply-to" on my git submission which 
caused the emails to be nested. I see now that you were referring to 
adding the urls to my submission.
I realize this is probably painful to go through over and over again 
with new contributors as they try to carefully follow all of the linux 
submission guidelines and I apologize for my ignorance.

> 
> I don't understand.
> 
> Are you going to ignore also Conor's tags?
> 
> Best regards,
> Krzysztof

  reply	other threads:[~2025-05-06 17:14 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
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 [this message]
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=043117e7-9fd7-4ddc-8fd9-433c5b8c5dc6@gmail.com \
    --to=inindev@gmail.com \
    --cc=andrew@lunn.ch \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=frattaroli.nicolas@gmail.com \
    --cc=heiko@sntech.de \
    --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