public inbox for linux-rockchip@lists.infradead.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,
	jonas@kwiboo.se, dsimic@manjaro.org, kever.yang@rock-chips.com,
	linux-rockchip@lists.infradead.org
Subject: Re: [PATCH v2 1/3] dt-bindings: arm: rockchip: add Radxa ROCK 5C
Date: Mon, 21 Oct 2024 08:10:12 +0200	[thread overview]
Message-ID: <5b8b2964-1fd4-4b56-a9c9-049ea0471bdb@kernel.org> (raw)
In-Reply-To: <20241020232956.1012-1-naoki@radxa.com>

On 21/10/2024 01:29, FUKAUMI Naoki wrote:
> Add devicetree binding for the Radxa ROCK 5C.
> 
> Radxa ROCK 5C is a 8K computer for everything[1] using the Rockchip
> RK3588S2 chip.
> 
> [1] https://radxa.com/products/rock5/5c
> 
> Signed-off-by: FUKAUMI Naoki <naoki@radxa.com>

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC. It might happen, that command when run on an older
kernel, gives you outdated entries. Therefore please be sure you base
your patches on recent Linux kernel.

Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.

You missed at least devicetree list (maybe more), so this won't be
tested by automated tooling. Performing review on untested code might be
a waste of time.

Please kindly resend and include all necessary To/Cc entries.
</form letter>

Best regards,
Krzysztof


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

      parent reply	other threads:[~2024-10-21  6:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-20 23:29 [PATCH v2 1/3] dt-bindings: arm: rockchip: add Radxa ROCK 5C FUKAUMI Naoki
2024-10-20 23:29 ` [PATCH v2 2/3] arm64: dts: " FUKAUMI Naoki
2024-10-20 23:29 ` [PATCH v2 3/3] arm64: dts: rockchip: Enable HDMI0 on rock-5c FUKAUMI Naoki
2024-10-21  6:10 ` Krzysztof Kozlowski [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=5b8b2964-1fd4-4b56-a9c9-049ea0471bdb@kernel.org \
    --to=krzk@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=dsimic@manjaro.org \
    --cc=heiko@sntech.de \
    --cc=jonas@kwiboo.se \
    --cc=kever.yang@rock-chips.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox