[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f54a40ea-99bf-e341-3bbd-851b250cc9cd@linaro.org>
Date: Thu, 29 Sep 2022 09:45:51 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Yinbo Zhu <zhuyinbo@...ngson.cn>,
"Rafael J . Wysocki" <rafael@...nel.org>,
Daniel Lezcano <daniel.lezcano@...aro.org>,
Amit Kucheria <amitk@...nel.org>,
Zhang Rui <rui.zhang@...el.com>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
linux-pm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: zhanghongchen <zhanghongchen@...ngson.cn>,
Liu Peibao <liupeibao@...ngson.cn>
Subject: Re: [PATCH v5 2/3] dt-bindings: thermal: add loongson2k thermal
binding
On 29/09/2022 09:07, Yinbo Zhu wrote:
>>>>>
>>>>> ... and please test your patches before sending :(
>>> You said is refer that "reg: [[0, 534779136], [0, 48]] is too long" ?
>>> Need fix that warning, right?
>>
>> Yes. You said you tested it but then sent with an error... so it's not
>> really a testing.
> sorry, I did do some testing. but I think It is okay that can generate a
> dtb without reporting an error when compile yaml file, in fact, I
> ignore the warning, I will fix it in v6.
Do you also send the code with warnings reported by GCC? Judging by
number of kernel test robot reports, it could be. So just to be very,
very clear: do not send any code which generates any warning. For GCC
this means W=1 builds.
Best regards,
Krzysztof
Powered by blists - more mailing lists