linux-kernel - Re: [PATCH RFC 2/6] ASoC: meson: audin: add audio input dt-bindings

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: <860f0bab-1f4b-4d4c-86c1-8a0ce389033c@kernel.org>
Date: Tue, 11 Feb 2025 08:33:03 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Valerio Setti <vsetti@...libre.com>, jbrunet@...libre.com,
 neil.armstrong@...aro.org, khilman@...libre.com,
 martin.blumenstingl@...glemail.com, linux-amlogic@...ts.infradead.org,
 linux-sound@...r.kernel.org
Cc: linux-kernel@...r.kernel.org
Subject: Re: [PATCH RFC 2/6] ASoC: meson: audin: add audio input dt-bindings

On 10/02/2025 16:01, Valerio Setti wrote:
> Add the dt-bindings and documentation of the AUDIN audio controller.
> This component provides most audio input found on the Amlogic GXBB SoC
> family.
> 
> Signed-off-by: Valerio Setti <vsetti@...libre.com>

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

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

(unless this RFC means you do not expect review)

Best regards,
Krzysztof