[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49dafe9afc5962d8fec10e6135c9b84d@manjaro.org>
Date: Mon, 29 Sep 2025 10:32:59 +0200
From: Dragan Simic <dsimic@...jaro.org>
To: guptarud@...il.com
Cc: Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>, Heiko Stuebner <heiko@...ech.de>,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-rockchip@...ts.infradead.org, linux-kernel@...r.kernel.org, Ondrej
Jirman <megi@....cz>, Martijn Braam <martijn@...xit.nl>, Kamil TrzciĆski <ayufan@...fan.eu>, "Leonardo G. Trombetta"
<lgtrombetta@....com>
Subject: Re: [PATCH v4 0/4] Upstreaming Pinephone Pro Patches
Hello Rudraksha,
On 2025-09-29 09:35, Rudraksha Gupta via B4 Relay wrote:
> arm64: dts: rk3399-pinephone-pro: Add light/proximity sensor
> support
> arm64: dts: rk3399-pinephone-pro: Add accelerometer sensor
> support
> arm64: dts: rk3399-pinephone-pro: Add magnetometer sensor support
> arm64: dts: rk3399-pinephone-pro: Fix voltage threshold for
> volume keys
Please note that the patch summaries/subjects are still a bit
wrong in the v4 of this series, because there should be no
"rk3399-pinephone-pro:" prefixes in them.
You can always check the commit history for the file you're
editing, to see what's the expected format of the patch summary.
It differs a bit between the subsystems and architectures, so
it should always be checked.
Powered by blists - more mailing lists