[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ffe2184066ddc9b4be4bf1bafc3497be@codeaurora.org>
Date: Fri, 24 Aug 2018 11:38:10 -0700
From: vnkgutta@...eaurora.org
To: Evan Green <evgreen@...omium.org>
Cc: robh@...nel.org, mchehab@...nel.org, linux-edac@...r.kernel.org,
linux-kernel@...r.kernel.org, Andy Gross <andy.gross@...aro.org>,
David Brown <david.brown@...aro.org>,
linux-arm-msm@...r.kernel.org, linux-soc@...r.kernel.org,
robh+dt@...nel.org, mark.rutland@....com,
devicetree@...r.kernel.org, tsoni@...eaurora.org,
ckadabi@...eaurora.org, rishabhb@...eaurora.org, bp@...en8.de
Subject: Re: [PATCH v2 3/4] drivers: edac: Add EDAC driver support for QCOM
SoCs
On 2018-08-23 16:07, Evan Green wrote:
> On Thu, Aug 23, 2018 at 4:04 PM Evan Green <evgreen@...omium.org>
> wrote:
>>
>> On Fri, Aug 17, 2018 at 5:08 PM Venkata Narendra Kumar Gutta
>> <vnkgutta@...eaurora.org> wrote:
>> >
>> > From: Channagoud Kadabi <ckadabi@...eaurora.org>
>
> Also checkpatch.pl complains a bit about this patch:
>
> WARNING: Non-standard signature: Co-developed-by:
> #14:
> Co-developed-by: Venkata Narendra Kumar Gutta
> <vnkgutta@...eaurora.org>
This needs to be there as the original author is Channagoud Kadabi
and I'm the one who is modifying and upstreaming this driver.
It was suggested to have this kind of signature from the earlier
patchset comments.
Can we do anything about this?
>
> WARNING: please write a paragraph that describes the
> config symbol fully
> #63: FILE: drivers/edac/Kconfig:460:
> +config EDAC_QCOM
This is also, I will check if I can get rid of this by writing more in
the description.
I don't really understand why do we need a paragraph here.
>
> WARNING: DT compatible string "qcom,llcc-edac" appears
> un-documented -- check ./Documentation/devicetree/bindings/
> #536: FILE: drivers/edac/qcom_edac.c:430:
> + { .compatible = "qcom,llcc-edac" },
This file is not added in the dt-bindings as there are no properties
(like reg-names or interrupts) for this driver
and anyway initialized from llcc driver.
Do we still need to have the Documentation in place?
>
> total: 0 errors, 3 warnings, 533 lines checked
>
> -Evan
Powered by blists - more mailing lists