From: Krzysztof Kozlowski <krzk@kernel.org>
To: Shimrra Shai <shimrrashai@gmail.com>
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v1 2/2] [Draft] dt-bindings: arm: rockchip: Add Firefly ITX-3588J board
Date: Fri, 13 Dec 2024 17:11:08 +0100 [thread overview]
Message-ID: <71cf636e-7124-4736-a63b-228394e9e149@kernel.org> (raw)
In-Reply-To: <20241213160337.5561-1-shimrrashai@gmail.com>
On 13/12/2024 17:03, Shimrra Shai wrote:
> On 2024-12-13, Shimrra Shai wrote:
>> As you said that is necessary "for automated tools to work"
>
> Correction to make an exact quotation: I meant to refer to when you said
> "so this won't be tested by automated tooling".
>
This was one form letter referring to one issue - you did not use the
tools to create correct CC/To address list. You split it unnecessarily
looking for some other meaning while it is still above one same thing.
DT list is a discussion or mailing list. Entire development is via
discussion lists.
Best regards,
Krzysztof
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
prev parent reply other threads:[~2024-12-13 16:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-13 1:30 [PATCH v1 0/2] [Draft] arm64: dts: rockchip: Add Firefly ITX-3588J Board Shimrra Shai
2024-12-13 1:30 ` [PATCH v1 1/2] [Draft] arm64: dts: rockchip: add DTs for Firefly ITX-3588J Shimrra Shai
2024-12-13 1:30 ` [PATCH v1 2/2] [Draft] dt-bindings: arm: rockchip: Add Firefly ITX-3588J board Shimrra Shai
2024-12-13 7:50 ` Krzysztof Kozlowski
2024-12-13 15:02 ` Shimrra Shai
2024-12-13 15:10 ` Krzysztof Kozlowski
2024-12-13 15:41 ` Re: " Shimrra Shai
2024-12-13 16:03 ` Shimrra Shai
2024-12-13 16:11 ` Krzysztof Kozlowski [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=71cf636e-7124-4736-a63b-228394e9e149@kernel.org \
--to=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=shimrrashai@gmail.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