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: <75b2db61-84ad-47a4-b809-da7e63e8dec8@kernel.org>
Date: Fri, 29 Aug 2025 12:31:59 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Dixit Parmar <dixitparmar19@...il.com>
Cc: Jonathan Cameron <jic23@...nel.org>, David Lechner
 <dlechner@...libre.com>, Nuno Sá <nuno.sa@...log.com>,
 Andy Shevchenko <andy@...nel.org>, Rob Herring <robh@...nel.org>,
 Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley
 <conor+dt@...nel.org>, linux-kernel@...r.kernel.org,
 linux-iio@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v5 1/2] iio: magnetometer: add support for Infineon
 TLV493D 3D Magentic sensor

On 29/08/2025 12:07, Dixit Parmar wrote:
>>> +INFINEON TLV493D Driver
>>> +M:   Dixit Parmar <dixitparmar19@...il.com>
>>> +L:   linux-iio@...r.kernel.org
>>> +S:   Maintained
>>> +W:   https://www.infineon.com/part/TLV493D-A1B6
>>> +F:   Documentation/devicetree/bindings/iio/magnetometer/infineon,tlv493d-a1b6.yaml
>>
>> There is no such file here. Apply this *patch* and check by yourself.
> That file is being added as a separate patch(Patch 2/2) of this same
> patch series. It's already reviewed by you only(based on the name).

No. Read my comment again:

"Apply this *patch* and check by yourself."

It does not matter if you add the file later. The file does not exist
now, here.

> https://lore.kernel.org/linux-iio/20250829-tlv493d-sensor-v6_16-rc5-v5-2-746e73bc6c11@gmail.com
>>
>> Your patchset is still incorrectly organized. See submitting patches in
>> DT dir.
> By "incorrectly organized" do you mean order of the patches in the
> patchset or anything else?

I pointed to the docs, is anything unclear in there?

Best regards,
Krzysztof

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ