From: Krzysztof Kozlowski <krzk@kernel.org>
To: Rodrigo Gobbi <rodrigo.gobbi.7@gmail.com>,
robh@kernel.org, krzk+dt@kernel.org, jic23@kernel.org,
dlechner@baylibre.com, nuno.sa@analog.com, andy@kernel.org,
conor+dt@kernel.org, mranostay@gmail.com, wbg@kernel.org
Cc: ~lkcamp/patches@lists.sr.ht, linux-iio@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/2] iio: proximity: update Lidar-lite v2 and create v3
Date: Mon, 3 Nov 2025 08:59:48 +0100 [thread overview]
Message-ID: <7349d741-7b6b-4736-a8d7-13fd3e7f1352@kernel.org> (raw)
In-Reply-To: <20251102221643.9966-1-rodrigo.gobbi.7@gmail.com>
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
prev parent reply other threads:[~2025-11-03 7:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-02 22:10 Rodrigo Gobbi
2025-11-02 22:10 ` [PATCH v3 1/2] dt-bindings: iio: proximity: Remove Lidar-lite-v2 from trivial Rodrigo Gobbi
2025-11-03 8:00 ` Krzysztof Kozlowski
2025-11-02 22:10 ` [PATCH v3 2/2] dt-bindings: iio: proximity: Add Lidar-lite-v2 and v3 Rodrigo Gobbi
2025-11-03 8:04 ` Krzysztof Kozlowski
2025-11-07 0:34 ` Rodrigo Gobbi
2025-11-03 7:59 ` Krzysztof Kozlowski [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7349d741-7b6b-4736-a8d7-13fd3e7f1352@kernel.org \
--to=krzk@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=jic23@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mranostay@gmail.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=rodrigo.gobbi.7@gmail.com \
--cc=wbg@kernel.org \
--cc=~lkcamp/patches@lists.sr.ht \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®