linux-kernel - Re: [PATCH] docs: devicetree: fix duplicated 'is is' in amlogic-dwmac and ti,dac7612

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <8a2b80f2-87a3-4446-b42e-7a985ef4bd10@kernel.org>
Date: Sun, 20 Jul 2025 14:33:16 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Sanjay Suthar <sanjaysuthar661996@...il.com>, linux-kernel@...r.kernel.org
Cc: dt-bindings@...ts.infradead.org, skhan@...uxfoundation.org,
 Neil Armstrong <neil.armstrong@...aro.org>,
 - Martin Blumenstingl <martin.blumenstingl@...glemail.com>
Subject: Re: [PATCH] docs: devicetree: fix duplicated 'is is' in amlogic-dwmac
 and ti,dac7612

On 19/07/2025 22:09, Sanjay Suthar wrote:
> Hi all,
> 
> This patch fixes a minor grammatical issue by removing duplicated "is is" in
> the Amlogic DWMAC and TI DAC7612 binding documentation files.

Your Cc is completely broken... Except maybe Neil and Martin.

<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>

Please use subject prefixes matching the subsystem. You can get them for
example with `git log --oneline -- DIRECTORY_OR_FILE` on the directory
your patch is touching. For bindings, the preferred subjects are
explained here:
https://www.kernel.org/doc/html/latest/devicetree/bindings/submitting-patches.html#i-for-patch-submitters

Also, please use standard way of sending patches, not as attachment. See
submitting patches.

Best regards,
Krzysztof