[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <9df703d9-b2c3-4978-9325-7ad50087e8f1@kernel.org>
Date: Tue, 10 Dec 2024 08:23:42 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Viken Dadhaniya <quic_vdadhani@...cinc.com>, andi.shyti@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
gregkh@...uxfoundation.org, jirislaby@...nel.org, broonie@...nel.or,
andersson@...nel.org, konradybcio@...nel.org, johan+linaro@...nel.org,
dianders@...omium.org, agross@...nel.org, linux-arm-msm@...r.kernel.org,
linux-i2c@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-serial@...r.kernel.org,
linux-spi@...r.kernel.org
Cc: quic_anupkulk@...cinc.com,
Mukesh Kumar Savaliya <quic_msavaliy@...cinc.com>
Subject: Re: [PATCH v1 1/7] dt-bindings: i2c: qcom,i2c-geni: Document DT
properties for QUP firmware loading
On 10/12/2024 05:43, Viken Dadhaniya wrote:
>>> maxItems: 1
>>>
>>> + qcom,load-firmware:
>>> + type: boolean
>>> + description: Optional property to load SE (serial engine) Firmware from protocol driver.
>>
>>
>> Please wrap code according to coding style (checkpatch is not a coding
>> style description, but only a tool).
> Actually i have ran dt-schema for yaml validation. I couldn't get if you
> have any comment for description statement OR it's related to code ?
> Could you please be more descriptive so i can adopt the suggestions.
This code is not conforming to coding style in terms of wrapping, what
dtschema has to do with it? Please read coding style.
Best regards,
Krzysztof
Powered by blists - more mailing lists