[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ded0c68a-e0b3-b106-e24d-7d9087c6ca4c@gmail.com>
Date: Tue, 2 May 2023 09:31:18 +0800
From: Jacky Huang <ychuang570808@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org,
lee@...nel.org, mturquette@...libre.com, sboyd@...nel.org,
p.zabel@...gutronix.de, gregkh@...uxfoundation.org,
jirislaby@...nel.org, tmaimon77@...il.com, catalin.marinas@....com,
will@...nel.org
Cc: devicetree@...r.kernel.org, linux-clk@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-serial@...r.kernel.org, arnd@...db.de, schung@...oton.com,
mjchen@...oton.com, Jacky Huang <ychuang3@...oton.com>
Subject: Re: [PATCH v8 05/11] dt-bindings: arm: Add initial bindings for
Nuvoton platform
Dear Krzysztof,
On 2023/5/1 下午 05:50, Krzysztof Kozlowski wrote:
> On 25/04/2023 12:24, Jacky Huang wrote:
>> From: Jacky Huang <ychuang3@...oton.com>
>>
>> Move 'nuvoton,npcm-gcr.yaml' from 'arm/npcm' to 'soc/nuvoton'.
>> Rename the '/arm/npcm' directory to 'arm/nuvoton'. Additionally, add
>> bindings for ARMv8-based Nuvoton SoCs and platform boards, and include
>> the initial bindings for ma35d1 series development boards.
>>
>> Signed-off-by: Jacky Huang <ychuang3@...oton.com>
>> ---
>> .../bindings/arm/nuvoton/nuvoton,ma35d1.yaml | 30 +++++++++++++++++++
>> .../npcm.yaml => nuvoton/nuvoton,npcm.yaml} | 2 +-
>> .../nuvoton/nuvoton,npcm-gcr.yaml} | 2 +-
>> 3 files changed, 32 insertions(+), 2 deletions(-)
>> create mode 100644 Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml
> I don't see any improvements here. Path in maintainers is still broken.
>
> Best regards,
> Krzysztof
>
Does this line cover
'Documentation/devicetree/bindings/arm/nuvoton/nuvoton,ma35d1.yaml'?
==> F: Documentation/devicetree/bindings/*/*/*ma35*
I ran 'get_maintainer.pl' on this patch, and it was able to find
maintainers and looked good.
I also ran 'make htmldocs' and did not see any warnings or errors
related to the .yaml files
in this patch. However, I am still unsure where the problem lies. Can
you suggest any
tools I can use to check for errors? I would greatly appreciate any
guidance you can provide.
Best Regards,
Jacky Huang
Powered by blists - more mailing lists