linux-kernel - Re: [PATCH 1/1] Fixing a minor typo in YAML document

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <62bd6757-c4d0-42c1-a76d-abea18a8a55e@kernel.org>
Date: Sat, 17 May 2025 13:21:27 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Jihed Chaibi <jihed.chaibi.dev@...il.com>, heiko@...ech.de,
 briannorris@...omium.org
Cc: devicetree@...r.kernel.org, linux-rockchip@...ts.infradead.org,
 linux-kernel-mentees@...ts.linux.dev, skhan@...uxfoundation.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] Fixing a minor typo in YAML document

On 17/05/2025 04:05, Jihed Chaibi wrote:
> A small typo in the rockchip,rk3399 YAML document ;
> "less then" should become: "less than"
> 
> Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@...il.com>
> ---
>  .../bindings/memory-controllers/rockchip,rk3399-dmc.yaml    | 6 +++---

You not only skipped me as DT maintainer for this file but also skipped
me as the actual subsystem maintainer.

<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). 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.
</form letter>

Best regards,
Krzysztof