All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Erik Beck <xunil@tahomasoft.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 v2a]: New board support,LinkStar-H68k-1432v1 (RK3568)
Date: Tue, 22 Jul 2025 23:36:47 -0500	[thread overview]
Message-ID: <20250723043647.GA1201956-robh@kernel.org> (raw)
In-Reply-To: <20250721201640.233818-1-xunil@tahomasoft.com>

On Mon, Jul 21, 2025 at 04:16:37PM -0400, Erik Beck wrote:
> Signed-off-by: Erik Beck <xunil@tahomasoft.com>

The threading of your emails is messed up. This is the only one in the 
thread. You need a commit messsage. Perhaps it can explain about this 
device/board some.

> ---
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
> index 5772d905f390..7f3904b69293 100644
> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> @@ -1109,6 +1109,11 @@ properties:
>            - const: rockchip,rk3588-toybrick-x0
>            - const: rockchip,rk3588
>  
> +      - description: Seeed LinkStar H68K-1432v1 RK3568
> +        items:
> +          - const: seeed,rk3568-linkstar-h68k-1432v1
> +          - const: rockchip,rk3568
> +
>        - description: Sinovoip RK3308 Banana Pi P2 Pro
>          items:
>            - const: sinovoip,rk3308-bpi-p2pro
> -- 
> 2.43.0
> 


WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Erik Beck <xunil@tahomasoft.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Heiko Stuebner <heiko@sntech.de>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2 v2a]: New board support,LinkStar-H68k-1432v1 (RK3568)
Date: Tue, 22 Jul 2025 23:36:47 -0500	[thread overview]
Message-ID: <20250723043647.GA1201956-robh@kernel.org> (raw)
In-Reply-To: <20250721201640.233818-1-xunil@tahomasoft.com>

On Mon, Jul 21, 2025 at 04:16:37PM -0400, Erik Beck wrote:
> Signed-off-by: Erik Beck <xunil@tahomasoft.com>

The threading of your emails is messed up. This is the only one in the 
thread. You need a commit messsage. Perhaps it can explain about this 
device/board some.

> ---
>  Documentation/devicetree/bindings/arm/rockchip.yaml | 5 +++++
>  1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/rockchip.yaml b/Documentation/devicetree/bindings/arm/rockchip.yaml
> index 5772d905f390..7f3904b69293 100644
> --- a/Documentation/devicetree/bindings/arm/rockchip.yaml
> +++ b/Documentation/devicetree/bindings/arm/rockchip.yaml
> @@ -1109,6 +1109,11 @@ properties:
>            - const: rockchip,rk3588-toybrick-x0
>            - const: rockchip,rk3588
>  
> +      - description: Seeed LinkStar H68K-1432v1 RK3568
> +        items:
> +          - const: seeed,rk3568-linkstar-h68k-1432v1
> +          - const: rockchip,rk3568
> +
>        - description: Sinovoip RK3308 Banana Pi P2 Pro
>          items:
>            - const: sinovoip,rk3308-bpi-p2pro
> -- 
> 2.43.0
> 

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

  reply	other threads:[~2025-07-23  4:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-21 20:16 [PATCH 1/2 v2a]: New board support,LinkStar-H68k-1432v1 (RK3568) Erik Beck
2025-07-21 20:16 ` Erik Beck
2025-07-23  4:36 ` Rob Herring [this message]
2025-07-23  4:36   ` Rob Herring

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=20250723043647.GA1201956-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=heiko@sntech.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=xunil@tahomasoft.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.