From: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
To: Vidhu Sarwal <vidhu.linux@gmail.com>,
Krzysztof Kozlowski <krzk@kernel.org>
Cc: "Rob Herring" <robh@kernel.org>,
"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Jonathan Cameron" <jic23@kernel.org>,
"David Lechner" <dlechner@baylibre.com>,
"Nuno Sá" <nuno.sa@analog.com>,
"Andy Shevchenko" <andy@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-iio@vger.kernel.org,
"Shuah Khan" <skhan@linuxfoundation.org>
Subject: Re: [PATCH v2 0/3] iio: proximity: Add Benewake TF-Luna LiDAR driver
Date: Mon, 2 Nov 2026 13:23:56 +0100 [thread overview]
Message-ID: <21b771dc-e9cd-46b9-a456-0950ae1270a3@oss.qualcomm.com> (raw)
In-Reply-To: <CAFqz8LJZQ+tw6wmLS-1FXvt6OxBESPEyz2-uK4D7B8X8epoKhg@mail.gmail.com>
On 02/11/2026 12:48, Vidhu Sarwal wrote:
> On Mon, Nov 02, 2026 at 11:47:56AM +0100, Krzysztof Kozlowski wrote:
>> What changed exactly? b4 diff fails, the patchset cannot be applied on
>> any known upstream revision I tried.
>
> I am really sorry for that, I didn't realise it was based on Jonathan's
> iio.git (testing branch) instead of linux-next. Patch 3 conflicts in the
That is fine in general, I'll wait for next linux-next.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-11-02 12:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 18:53 Vidhu Sarwal via B4 Relay
2026-10-30 18:53 ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: Add Benewake Vidhu Sarwal via B4 Relay
2026-10-30 18:53 ` [PATCH v2 2/3] dt-bindings: iio: proximity: Add Benewake TF-Luna Vidhu Sarwal via B4 Relay
2026-11-02 10:47 ` Krzysztof Kozlowski
2026-10-30 18:53 ` [PATCH v2 3/3] iio: proximity: Add Benewake TF-Luna LiDAR driver Vidhu Sarwal via B4 Relay
2026-10-31 14:51 ` Andy Shevchenko
2026-10-31 23:22 ` Jonathan Cameron
2026-11-02 10:47 ` [PATCH v2 0/3] " Krzysztof Kozlowski
2026-11-02 11:48 ` Vidhu Sarwal
2026-11-02 12:23 ` Krzysztof Kozlowski [this message]
2026-11-02 22:20 ` Jonathan Cameron
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=21b771dc-e9cd-46b9-a456-0950ae1270a3@oss.qualcomm.com \
--to=krzysztof.kozlowski@oss.qualcomm.com \
--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=krzk@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=skhan@linuxfoundation.org \
--cc=vidhu.linux@gmail.com \
/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®