All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Prabhakar <prabhakar.csengg@gmail.com>,
	Biju Das <biju.das.jz@bp.renesas.com>
Subject: Re: [PATCH] dt-bindings: soc: renesas: Move renesas.yaml from arm to soc
Date: Tue, 16 Aug 2022 11:41:50 -0600	[thread overview]
Message-ID: <20220816174150.GA2428940-robh@kernel.org> (raw)
In-Reply-To: <20220815111708.22302-1-prabhakar.mahadev-lad.rj@bp.renesas.com>

On Mon, Aug 15, 2022 at 12:17:08PM +0100, Lad Prabhakar wrote:
> 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.

Please post this as part of the above.

bindings/soc/ is just a dumping ground for stuff that doesn't fit 
anywhere. We've mostly cleaned bindings/arm/ of that, so I don't really 
want to start that again. I would propose bindings/board/ instead if we 
move in this direction.

> 
> 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@bp.renesas.com>
> ---
>  .../devicetree/bindings/{arm => soc/renesas}/renesas.yaml       | 2 +-
>  MAINTAINERS                                                     | 1 -
>  2 files changed, 1 insertion(+), 2 deletions(-)
>  rename Documentation/devicetree/bindings/{arm => soc/renesas}/renesas.yaml (99%)
> 
> diff --git a/Documentation/devicetree/bindings/arm/renesas.yaml b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> similarity index 99%
> rename from Documentation/devicetree/bindings/arm/renesas.yaml
> rename to Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> index ff80152f092f..7aae35c5f6aa 100644
> --- a/Documentation/devicetree/bindings/arm/renesas.yaml
> +++ b/Documentation/devicetree/bindings/soc/renesas/renesas.yaml
> @@ -1,7 +1,7 @@
>  # SPDX-License-Identifier: GPL-2.0
>  %YAML 1.2
>  ---
> -$id: http://devicetree.org/schemas/arm/renesas.yaml#
> +$id: http://devicetree.org/schemas/soc/renesas/renesas.yaml#
>  $schema: http://devicetree.org/meta-schemas/core.yaml#
>  
>  title: Renesas SH-Mobile, R-Mobile, and R-Car Platform Device Tree Bindings
> diff --git a/MAINTAINERS b/MAINTAINERS
> index e3058091899f..e42a7524e3f1 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -2658,7 +2658,6 @@ S:	Supported
>  Q:	http://patchwork.kernel.org/project/linux-renesas-soc/list/
>  C:	irc://irc.libera.chat/renesas-soc
>  T:	git git://git.kernel.org/pub/scm/linux/kernel/git/geert/renesas-devel.git next
> -F:	Documentation/devicetree/bindings/arm/renesas.yaml
>  F:	Documentation/devicetree/bindings/hwinfo/renesas,prr.yaml
>  F:	Documentation/devicetree/bindings/soc/renesas/
>  F:	arch/arm64/boot/dts/renesas/
> -- 
> 2.17.1
> 
> 

  reply	other threads:[~2022-08-16 17:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-15 11:17 [PATCH] dt-bindings: soc: renesas: Move renesas.yaml from arm to soc Lad Prabhakar
2022-08-16 17:41 ` Rob Herring [this message]
2022-08-16 18:40   ` Lad, Prabhakar
2022-08-16 20:43     ` Rob Herring
2022-08-17  9:30   ` Geert Uytterhoeven
2022-08-18  8:42     ` Krzysztof Kozlowski
2022-08-17  1:31 ` kernel test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220816174150.GA2428940-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=biju.das.jz@bp.renesas.com \
    --cc=devicetree@vger.kernel.org \
    --cc=geert+renesas@glider.be \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=prabhakar.csengg@gmail.com \
    --cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.