linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Aleksander Jan Bajkowski <olek2@wp.pl>
Cc: robh+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
	devicetree@vger.kernel.org, linux-mips@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: dts: lantiq: rename dts files with soc name being the prefix
Date: Mon, 26 Sep 2022 11:08:40 +0200	[thread overview]
Message-ID: <20220926090840.GA6352@alpha.franken.de> (raw)
In-Reply-To: <20220829183717.4394-1-olek2@wp.pl>

On Mon, Aug 29, 2022 at 08:37:17PM +0200, Aleksander Jan Bajkowski wrote:
> Rename lantiq dts files with soc name being the prefix, so that the
> board dts file can be located easily by soc name, and we also gain
> the consistency of naming.
> 
> This patch is a preparation for the addition of dts for newer SoCs
> (Lantiq ARX100, VRX200 and xRX330).
> 
> Signed-off-by: Aleksander Jan Bajkowski <olek2@wp.pl>
> ---
>  arch/mips/boot/dts/lantiq/Makefile                              | 2 +-
>  .../boot/dts/lantiq/{easy50712.dts => danube_easy50712.dts}     | 0
>  2 files changed, 1 insertion(+), 1 deletion(-)
>  rename arch/mips/boot/dts/lantiq/{easy50712.dts => danube_easy50712.dts} (100%)
> 
> diff --git a/arch/mips/boot/dts/lantiq/Makefile b/arch/mips/boot/dts/lantiq/Makefile
> index f5dfc06242b9..ae6e3e21ebeb 100644
> --- a/arch/mips/boot/dts/lantiq/Makefile
> +++ b/arch/mips/boot/dts/lantiq/Makefile
> @@ -1,4 +1,4 @@
>  # SPDX-License-Identifier: GPL-2.0
> -dtb-$(CONFIG_DT_EASY50712)	+= easy50712.dtb
> +dtb-$(CONFIG_DT_EASY50712)	+= danube_easy50712.dtb
>  
>  obj-$(CONFIG_BUILTIN_DTB)	+= $(addsuffix .o, $(dtb-y))
> diff --git a/arch/mips/boot/dts/lantiq/easy50712.dts b/arch/mips/boot/dts/lantiq/danube_easy50712.dts
> similarity index 100%
> rename from arch/mips/boot/dts/lantiq/easy50712.dts
> rename to arch/mips/boot/dts/lantiq/danube_easy50712.dts
> -- 
> 2.30.2

applied to mips-next.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

      reply	other threads:[~2022-09-26  9:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-29 18:37 [PATCH] MIPS: dts: lantiq: rename dts files with soc name being the prefix Aleksander Jan Bajkowski
2022-09-26  9:08 ` Thomas Bogendoerfer [this message]

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=20220926090840.GA6352@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=olek2@wp.pl \
    --cc=robh+dt@kernel.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).