Re: [PATCH 1/2] arm64: dts: qcom: minor whitespace cleanup around '='

From: Krzysztof Kozlowski
Date: Mon Jul 03 2023 - 12:08:27 EST


On 03/07/2023 11:56, Konrad Dybcio wrote:
>>>> diff --git a/arch/arm64/boot/dts/qcom/msm8939.dtsi b/arch/arm64/boot/dts/qcom/msm8939.dtsi
>>>> index 895cafc11480..c4209e2d4b4e 100644
>>>> --- a/arch/arm64/boot/dts/qcom/msm8939.dtsi
>>>> +++ b/arch/arm64/boot/dts/qcom/msm8939.dtsi
>>>> @@ -155,7 +155,7 @@ CPU7: cpu@3 {
>>>>
>>>> idle-states {
>>>> CPU_SLEEP_0: cpu-sleep-0 {
>>>> - compatible ="qcom,idle-state-spc", "arm,idle-state";
>>>> + compatible = "qcom,idle-state-spc", "arm,idle-state";
>>> Will conflict with:
>>>
>>> https://lore.kernel.org/linux-arm-msm/20230627-topic-more_bindings-v1-2-6b4b6cd081e5@xxxxxxxxxx/
>>>
>>> there are also a couple of entries with property =\n\t{n}[a-z]
>>>
>>> Otherwise lgtm
>>
>> Konrad, please remember to trim irrelevant context from your replies
>> (e.g. so that we don't have to skim through thousands of lines to find
>> a single comment).
> My actual reply begins at line 77, which is considerably less than
> thousands and is concluded by my signoff, which signifies the end
> of the message.

Your reply did not start at first scroll page. I had to scroll. Since
you put your reply inside big chunks of quote, it's very easy to miss
it. So I keep scrolling, keep scrolling, and so on, so on. Till I reach
end of email and I still don't see your reply.

Now in this email it was easy to find, because it was more than one
line. But in other responses I waste some time to find yours. Johan's
comment is here perfectly valid. Reading your responses is more time
consuming than required.

Best regards,
Krzysztof