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: <99e89fb4-e99e-4a0f-8058-0ef6f04d61d8@linaro.org>
Date:   Wed, 29 Nov 2023 09:47:57 +0100
From:   Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To:     Petre Rodan <petre.rodan@...dimension.ro>
Cc:     linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org,
        devicetree@...r.kernel.org, Conor Dooley <conor+dt@...nel.org>,
        Lars-Peter Clausen <lars@...afoo.de>,
        Rob Herring <robh+dt@...nel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
        linux-kernel-mentees@...ts.linuxfoundation.org,
        Jonathan Cameron <jic23@...nel.org>
Subject: Re: [PATCH v5 1/2] dt-bindings: iio: pressure: add honeywell,hsc030

On 29/11/2023 09:44, Petre Rodan wrote:
> 
> hi,
> 
> On Wed, Nov 29, 2023 at 09:04:17AM +0100, Krzysztof Kozlowski wrote:
>> On 29/11/2023 08:04, Petre Rodan wrote:
>>> Adds binding for digital Honeywell TruStability HSC and SSC series
>>> pressure and temperature sensors.
>>> Communication is one way. The sensor only requires 4 bytes worth of
>>> clock pulses on both i2c and spi in order to push the data out.
>>> The i2c address is hardcoded and depends on the part number.
>>> There is no additional GPIO control.
>>
>> Your threading is broken (not existing) since v4, making it difficult to
>> apply the patchset. Please fix it when sending v6.
> 
> I'm confused.
> 
> you mean the lack of 'In-Reply-To' and 'References' headers in the emails
> `git send-email` is generating?
> I've added them for v2, but was told that was a mistake [1]
> 
> [1] https://lore.kernel.org/lkml/20231125191915.7f1f2dc4@jic23-huawei/
> 
> I'm probably misunderstanding something.
> also, I hope v5 is flawless enough.

No, v5 is still wrong. Patchset should be threaded. Open lore.kernel.org
and look how patchsets are organized and how your patchset is done.

It is as simple as:
git format-patch -v6 -2
scripts/get_maintainers.pl
git send-email v6*

(I combine the last two steps, so I don't even bother with
script/maintainers:
https://github.com/krzk/tools/blob/master/linux/.bash_aliases_linux#L91 )

But actually you should use b4, which also does this job correctly for you.

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ