linux-kernel - Re: [PATCH v3 01/10] dt-bindings: soc: renesas: Move renesas.yaml from arm to soc

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <CA+V-a8u8NdzaOmnQocAi_tthE=J_-LabG49StxH3gyV2QJwirQ@mail.gmail.com>
Date:   Thu, 15 Sep 2022 22:56:43 +0100
From:   "Lad, Prabhakar" <prabhakar.csengg@...il.com>
To:     Conor.Dooley@...rochip.com
Cc:     geert+renesas@...der.be, robh+dt@...nel.org,
        krzysztof.kozlowski+dt@...aro.org, paul.walmsley@...ive.com,
        palmer@...belt.com, aou@...s.berkeley.edu, heiko@...ech.de,
        atishp@...osinc.com, devicetree@...r.kernel.org,
        linux-riscv@...ts.infradead.org, linux-renesas-soc@...r.kernel.org,
        linux-kernel@...r.kernel.org, biju.das.jz@...renesas.com,
        prabhakar.mahadev-lad.rj@...renesas.com
Subject: Re: [PATCH v3 01/10] dt-bindings: soc: renesas: Move renesas.yaml
 from arm to soc

Hi Conor,

Thank you for the review.

On Thu, Sep 15, 2022 at 10:13 PM <Conor.Dooley@...rochip.com> wrote:
>
> On 15/09/2022 19:15, Prabhakar wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> >
> > From: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
> >
> > renesas.yaml lists out all the Renesas SoC's and the platforms/EVK's which
> > is either ARM32/ARM64. It would rather make sense if we move renesas.yaml
> > to the soc/renesas folder instead. This is in preparation for adding a new
> > SoC (RZ/Five) from Renesas which is based on RISC-V.
> >
> > While at it drop the old entry for renesas.yaml from MAINTAINERS file and
> > there is no need to update the new file path of renesas.yaml as we already
> > have an entry for Documentation/devicetree/bindings/soc/renesas/ folder.
> >
> > Signed-off-by: Lad Prabhakar <prabhakar.mahadev-lad.rj@...renesas.com>
> > ---
> > v3:
> > * New patch along with this series previously posted as a standalone
> > patch [0].
> >
> > [0] https://patchwork.kernel.org/project/linux-renesas-soc/patch/20220815111708.22302-1-prabhakar.mahadev-lad.rj@bp.renesas.com/
> > ---
> >  .../devicetree/bindings/{arm => soc/renesas}/renesas.yaml        | 0
> >  MAINTAINERS                                                      | 1 -
> >  2 files changed, 1 deletion(-)
> >  rename Documentation/devicetree/bindings/{arm => soc/renesas}/renesas.yaml (100%)
>
> Got one error from the rename:
> /stuff/linux/Documentation/devicetree/bindings/soc/renesas/renesas.yaml: $id: relative path/filename doesn't match actual path or filename
>         expected: http://devicetree.org/schemas/soc/renesas/renesas.yaml#
>
Argh, how did I miss that!

Cheers,
Prabhakar