linux-kernel - Re: [PATCH] dt-bindings: iio: pressure: invensense,icp101xx: add binding

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: <87dddb35-6132-4417-8fe0-09b0df2f870c@kernel.org>
Date: Fri, 27 Jun 2025 07:53:46 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Rodrigo Gobbi <rodrigo.gobbi.7@...il.com>, jic23@...nel.org,
 dlechner@...libre.com, nuno.sa@...log.com, andy@...nel.org,
 jmaneyrol@...ensense.com
Cc: ~lkcamp/patches@...ts.sr.ht, linux-iio@...r.kernel.org,
 linux-kernel@...r.kernel.org
Subject: Re: [PATCH] dt-bindings: iio: pressure: invensense,icp101xx: add
 binding

On 26/06/2025 23:12, Rodrigo Gobbi wrote:
> There is no txt file for it, add yaml for invensense,icp101xx family
> which is already used in the driver.
> 
> Signed-off-by: Rodrigo Gobbi <rodrigo.gobbi.7@...il.com>
> ---
> Very simple yaml for a i2c device with psu. The pin out for the rest of
> the family (the other PNs) doesn`t change anything here, since the diff
> were RESV pins (unused).

Filename matching compatible, please.

<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