[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7349d741-7b6b-4736-a8d7-13fd3e7f1352@kernel.org>
Date: Mon, 3 Nov 2025 08:59:48 +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 0/2] iio: proximity: update Lidar-lite v2 and create v3
On 02/11/2025 23:10, Rodrigo Gobbi wrote:
> This series moves the Lidar v2 binding from trivial to a dedicated place.
> It also adds the v3, which was not described yet, in the same place since
> it's the same hardware and it is already supported by the driver.
> ---
> Hi, all,
> Very few changes in this v3. At the v2 link, there was a discussion about
> the PWM output pin and the current support of that. It was suggested to
> not add that pin here, at least for now.
> Tks and regards.
>
> Changelog:
> v3: split things in a patchset
Hm? Why. That's non-bisectable now
Best regards,
Krzysztof
Powered by blists - more mailing lists