From: Shimrra Shai <shimrrashai@gmail.com>
To: krzk@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
linux-rockchip@lists.infradead.org, shimrrashai@gmail.com
Subject: Re: Re: Re: [PATCH v1 2/2] [Draft] dt-bindings: arm: rockchip: Add Firefly ITX-3588J board
Date: Fri, 13 Dec 2024 09:41:14 -0600 [thread overview]
Message-ID: <20241213154114.5078-1-shimrrashai@gmail.com> (raw)
In-Reply-To: <ca3f43f8-f96a-4d2b-9273-a4d936fab6a6@kernel.org>
On 2024-12-13, Krzysztof Kozlowski wrote:
> I mean exactly what is written. Use the tools and the tools will do the
> job.
Since the remainder of your post is talking about CCs and the only other
tools listed are related to CCs does this mean that by "device tree list"
you were referring to a place to send messages, not a file in the source
code with a list of device trees in it? I was interpreting your statement
as referring to the latter, not the former. You also mentioned things being
wrong with the code, too, even though they did not show up on the scripts/
checkpatch.pl tool.
> This does not work like this. Use the tools, not other people's
> incorrect CC list.
> I gave you instruction which tools to use, so I do not understand why do
> you insist on not using them.
I am having trouble understanding is why. Are you talking about messaging
or a part of the source code itself when you say "device tree list"? As you
said that is necessary "for automated tools to work" and that makes me
think it's some part of the source code run by such a tool, but here you
are talking about "CC lists" i.e. messaging. So I do not understand what
that word is referring to - that is my confusion. I certainly can use those
CC tools but if there is also something that needs change in the code it
won't be changed unless I know exactly what that is and thus I need to know
if there are any outstanding code changes indicated before I make another
submission using the CC tools.
Shimrra
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2024-12-13 15:41 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 ` Shimrra Shai [this message]
2024-12-13 16:03 ` Re: Re: " Shimrra Shai
2024-12-13 16:11 ` Krzysztof Kozlowski
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=20241213154114.5078-1-shimrrashai@gmail.com \
--to=shimrrashai@gmail.com \
--cc=krzk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.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