All of lore.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: FUKAUMI Naoki <naoki@radxa.com>, heiko@sntech.de
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 2/3] arm64: dts: rockchip: prepare common .dtsi for Radxa ROCK Pi E
Date: Sun, 23 Jun 2024 14:09:16 +0200	[thread overview]
Message-ID: <094882f5-48e6-4c0d-b6c6-942cc21e14bd@kernel.org> (raw)
In-Reply-To: <20240623120016.82990-2-naoki@radxa.com>

On 23/06/2024 14:00, FUKAUMI Naoki wrote:
> Radxa ROCK Pi E v1.2x and ROCK Pi E v3.0 share most of their parts.
> prepare rk3328-rock-pi-e-base.dtsi as a common dtsi for both boards.
> 
> Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>
> ---
>  .../{rk3328-rock-pi-e.dts => rk3328-rock-pi-e-base.dtsi}       | 3 ---
>  1 file changed, 3 deletions(-)
>  rename arch/arm64/boot/dts/rockchip/{rk3328-rock-pi-e.dts => rk3328-rock-pi-e-base.dtsi} (99%)

This breaks users and is not bisectable.

Best regards,
Krzysztof


_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

WARNING: multiple messages have this Message-ID (diff)
From: Krzysztof Kozlowski <krzk@kernel.org>
To: FUKAUMI Naoki <naoki@radxa.com>, heiko@sntech.de
Cc: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org
Subject: Re: [PATCH 2/3] arm64: dts: rockchip: prepare common .dtsi for Radxa ROCK Pi E
Date: Sun, 23 Jun 2024 14:09:16 +0200	[thread overview]
Message-ID: <094882f5-48e6-4c0d-b6c6-942cc21e14bd@kernel.org> (raw)
In-Reply-To: <20240623120016.82990-2-naoki@radxa.com>

On 23/06/2024 14:00, FUKAUMI Naoki wrote:
> Radxa ROCK Pi E v1.2x and ROCK Pi E v3.0 share most of their parts.
> prepare rk3328-rock-pi-e-base.dtsi as a common dtsi for both boards.
> 
> Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>
> ---
>  .../{rk3328-rock-pi-e.dts => rk3328-rock-pi-e-base.dtsi}       | 3 ---
>  1 file changed, 3 deletions(-)
>  rename arch/arm64/boot/dts/rockchip/{rk3328-rock-pi-e.dts => rk3328-rock-pi-e-base.dtsi} (99%)

This breaks users and is not bisectable.

Best regards,
Krzysztof


  reply	other threads:[~2024-06-23 12:09 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-23 12:00 [PATCH 1/3] dt-bindings: arm: rockchip: Add Radxa ROCK Pi E v3.0 FUKAUMI Naoki
2024-06-23 12:00 ` FUKAUMI Naoki
2024-06-23 12:00 ` [PATCH 2/3] arm64: dts: rockchip: prepare common .dtsi for Radxa ROCK Pi E FUKAUMI Naoki
2024-06-23 12:00   ` FUKAUMI Naoki
2024-06-23 12:09   ` Krzysztof Kozlowski [this message]
2024-06-23 12:09     ` Krzysztof Kozlowski
2024-06-23 12:00 ` [PATCH 3/3] arm64: dts: rockchip: add support for Radxa ROCK Pi E v3.0 FUKAUMI Naoki
2024-06-23 12:00   ` FUKAUMI Naoki
2024-06-23 12:09   ` Krzysztof Kozlowski
2024-06-23 12:09     ` Krzysztof Kozlowski
2024-06-23 12:08 ` [PATCH 1/3] dt-bindings: arm: rockchip: Add " Krzysztof Kozlowski
2024-06-23 12:08   ` Krzysztof Kozlowski
2024-06-23 12:11   ` FUKAUMI Naoki
2024-06-23 12:11     ` FUKAUMI Naoki

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=094882f5-48e6-4c0d-b6c6-942cc21e14bd@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=naoki@radxa.com \
    --cc=robh@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 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.