[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d30dc192-e37d-49d6-97c7-26e90a7ae6f9@kernel.org>
Date: Mon, 3 Nov 2025 09:04:21 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Rodrigo Gobbi <rodrigo.gobbi.7@...il.com>, robh@...nel.org,
krzk+dt@...nel.org, jic23@...nel.org, dlechner@...libre.com,
nuno.sa@...log.com, andy@...nel.org, conor+dt@...nel.org,
mranostay@...il.com, wbg@...nel.org
Cc: ~lkcamp/patches@...ts.sr.ht, linux-iio@...r.kernel.org,
linux-kernel@...r.kernel.org, devicetree@...r.kernel.org
Subject: Re: [PATCH v3 2/2] dt-bindings: iio: proximity: Add Lidar-lite-v2 and
v3
On 02/11/2025 23:10, Rodrigo Gobbi wrote:
> Since v2 is not a trivial device, add it to a dedicated place. The v3 is
What is v2 and v3? This patchset is v3, don't refer to it in the commit
msg. If you speak about devices then make it obvious. How anyone going
through `git log` can figure out what is v2. Your patch mentions some v2
and v3 but these are different companies, so somehow completely
different products?
> similar to the v2 version, so add it as a fallback to the v2. Both versions
> are already supported by the driver.
Best regards,
Krzysztof
Powered by blists - more mailing lists