Hi Conor, Thank you for the review. On Thu, Sep 15, 2022 at 10:13 PM <Conor.Dooley@xxxxxxxxxxxxx> 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@xxxxxxxxxxxxxx> > > > > 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@xxxxxxxxxxxxxx> > > --- > > 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@xxxxxxxxxxxxxx/ > > --- > > .../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
