linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Magnus Damm <damm@opensource.se>, linux-renesas-soc@vger.kernel.org
Cc: wsa+renesas@sang-engineering.com, geert+renesas@glider.be
Subject: Re: [PATCH 1/6] dt-bindings: memory-controllers: renesas,rpc-if: Add RZ compat str
Date: Sun, 6 Jul 2025 09:25:20 +0200	[thread overview]
Message-ID: <2e4e032c-ba65-4a10-85f8-1d36658423e0@kernel.org> (raw)
In-Reply-To: <175174253155.83411.3250526926071589353.sendpatchset@1.0.0.127.in-addr.arpa>

On 05/07/2025 21:08, Magnus Damm wrote:
> From: Magnus Damm <damm@opensource.se>
> 
> Add RZ/A1 and RZ/A2 compat strings for the renesas rpc-if device.
> 
> Signed-off-by: Magnus Damm <damm@opensource.se>

You not only skipped maintainers of the subsystem, but also DT
maintainers... and you never tested it. Eh...


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.


It does not look like you tested the bindings, at least after quick
look. Please run `make dt_binding_check` (see
Documentation/devicetree/bindings/writing-schema.rst for instructions).
Maybe you need to update your dtschema and yamllint. Don't rely on
distro packages for dtschema and be sure you are using the latest
released dtschema.


Best regards,
Krzysztof

  reply	other threads:[~2025-07-06  7:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-05 19:08 [PATCH 0/6] Add rpc-if to RZ/A1, RZ/A2 and update/add board support Magnus Damm
2025-07-05 19:08 ` [PATCH 1/6] dt-bindings: memory-controllers: renesas,rpc-if: Add RZ compat str Magnus Damm
2025-07-06  7:25   ` Krzysztof Kozlowski [this message]
2025-07-05 19:08 ` [PATCH 2/6] ARM: dts: renesas: r7s72100: add rpc-if nodes Magnus Damm
2025-07-05 19:09 ` [PATCH 3/6] ARM: dts: renesas: r7s9210: add rpc-if node Magnus Damm
2025-07-05 19:09 ` [PATCH 4/6] ARM: dts: renesas: genmai: add rpc-if SPI NOR flash Magnus Damm
2025-07-07 12:20   ` Geert Uytterhoeven
2025-07-08 20:26     ` Wolfram Sang
2025-07-10 18:08       ` Magnus Damm
2025-07-30 13:17         ` Geert Uytterhoeven
2025-07-05 19:09 ` [PATCH 5/6] ARM: dts: renesas: gr-mango: initial board support Magnus Damm
2025-08-18 11:57   ` Geert Uytterhoeven
2025-07-05 19:09 ` [PATCH 6/6] ARM: dts: renesas: rza2mbtc: " Magnus Damm
2025-07-06  7:26   ` Krzysztof Kozlowski
2025-07-07 17:55 ` [PATCH 0/6] Add rpc-if to RZ/A1, RZ/A2 and update/add " Rob Herring (Arm)

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=2e4e032c-ba65-4a10-85f8-1d36658423e0@kernel.org \
    --to=krzk@kernel.org \
    --cc=damm@opensource.se \
    --cc=geert+renesas@glider.be \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=wsa+renesas@sang-engineering.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 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).