[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1465f4d2-efe1-44f7-a4f9-ef4a7c271b2c@oss.qualcomm.com>
Date: Tue, 25 Nov 2025 11:48:25 +0100
From: Konrad Dybcio <konrad.dybcio@....qualcomm.com>
To: guptarud@...il.com, Bjorn Andersson <andersson@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley
<conor+dt@...nel.org>,
Jonathan Cameron <jic23@...nel.org>,
David Lechner <dlechner@...libre.com>,
Nuno Sá
<nuno.sa@...log.com>,
Andy Shevchenko <andy@...nel.org>
Cc: linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-iio@...r.kernel.org
Subject: Re: [PATCH v4 0/6] ARM: dts: qcom: msm8960: expressatt: Add more
peripherals
On 11/25/25 12:35 AM, Rudraksha Gupta via B4 Relay wrote:
> Intro:
[...]
> Changes in v4:
> - corrected accelerometer's mount matrix
> - fix a nullptr issue in the accelerometer's driver code
The patches are now:
1 dt
2 dt
3 dt
4 dt
5 iio (different tree/maintainer)
6 dt
Which makes it non-obvious how to merge them, especially given 5 seems
like a pre-requisite for 6 if you don't like nullptrs
If that's the case (although I would like to think 5 isn't really
necessary because board designers generally don't randomly omit
connecting interrupt pins), it would be best if you first sent 1-4 and
then 5-6 as a follow-up in a new series.
For now, let's try to settle whether you really need 5
Konrad
Powered by blists - more mailing lists