From: Bjorn Andersson <andersson@kernel.org>
To: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Casey Connolly <casey.connolly@linaro.org>,
David Heidelberg <david@ixit.cz>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Regulator adjustments for OnePlus 6 and 6T
Date: Mon, 5 Jan 2026 08:07:14 -0600 [thread overview]
Message-ID: <176762206411.2923194.1176119791295581298.b4-ty@kernel.org> (raw)
In-Reply-To: <20251118-dts-oneplus-regulators-v2-0-3e67cea1e4e7@ixit.cz>
On Tue, 18 Nov 2025 15:52:24 +0100, David Heidelberg wrote:
> Small regulators adjustments, tested on sdm845-mainline and sdm845-next
> tree with recently fixed (6) and upstreamed (6T) drivers.
>
>
Applied, thanks!
[1/3] arm64: dts: qcom: sdm845-oneplus: Don't mark ts supply boot-on
commit: c9b98b9dad9749bf2eb7336a6fca31a6af1039d7
[2/3] arm64: dts: qcom: sdm845-oneplus: Don't keep panel regulator always on
commit: 45d1f42d3e84b5880cf9fab1eb24a7818320eeb7
[3/3] arm64: dts: qcom: sdm845-oneplus: Mark l14a regulator as boot-on
commit: ad33ee060be46794a03d033894c9db3a9d6c1a0f
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-01-05 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-18 14:52 David Heidelberg via B4 Relay
2025-11-18 14:52 ` [PATCH v2 1/3] arm64: dts: qcom: sdm845-oneplus: Don't mark ts supply boot-on David Heidelberg via B4 Relay
2025-11-18 15:02 ` Konrad Dybcio
2025-11-18 14:52 ` [PATCH v2 2/3] arm64: dts: qcom: sdm845-oneplus: Don't keep panel regulator always on David Heidelberg via B4 Relay
2025-11-18 15:02 ` Konrad Dybcio
2025-11-18 14:52 ` [PATCH v2 3/3] arm64: dts: qcom: sdm845-oneplus: Mark l14a regulator as boot-on David Heidelberg via B4 Relay
2025-11-18 15:02 ` Konrad Dybcio
2026-01-05 14:07 ` Bjorn Andersson [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=176762206411.2923194.1176119791295581298.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=casey.connolly@linaro.org \
--cc=conor+dt@kernel.org \
--cc=david@ixit.cz \
--cc=devicetree@vger.kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=robh@kernel.org \
/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®