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>,
David Heidelberg <david@ixit.cz>
Cc: Paul Sajna <sajattack@postmarketos.org>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH RFC 0/2] sdm845: describe the Wi-Fi hardware properly
Date: Mon, 30 Mar 2026 11:01:16 -0500 [thread overview]
Message-ID: <177488647763.633011.11795865171145683746.b4-ty@kernel.org> (raw)
In-Reply-To: <20260327-wcn3990-pwrctl-sdm845-v1-0-3f5c34e3fdd0@ixit.cz>
On Fri, 27 Mar 2026 14:07:07 +0100, David Heidelberg wrote:
> Question here is, if the most of the wcn3990-pmu shouldn't rather go to
> sdm845.dtsi? At least the regulators seems to be same.
>
> When agreed, I'll sent include all other sdm845 phones in the patchset.
>
>
Applied, thanks!
[1/2] arm64: dts: qcom: sdm845-google: Describe Wi-Fi/BT properly
commit: 0a9c8715663998dc4d8eaa8f1a40440214906d96
[2/2] arm64: dts: qcom: sdm845-oneplus: Describe Wi-Fi/BT properly
commit: 7a4790b1a2c9ff66bd7a95d8761d5e9fc9334ba9
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2026-03-30 16:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-27 13:07 [PATCH RFC 0/2] sdm845: describe the Wi-Fi hardware properly David Heidelberg via B4 Relay
2026-03-27 13:07 ` [PATCH RFC 1/2] arm64: dts: qcom: sdm845-google: Describe Wi-Fi/BT properly David Heidelberg via B4 Relay
2026-03-27 23:35 ` Dmitry Baryshkov
2026-03-27 13:07 ` [PATCH RFC 2/2] arm64: dts: qcom: sdm845-oneplus: " David Heidelberg via B4 Relay
2026-03-27 23:34 ` Dmitry Baryshkov
2026-03-30 16:01 ` 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=177488647763.633011.11795865171145683746.b4-ty@kernel.org \
--to=andersson@kernel.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=robh@kernel.org \
--cc=sajattack@postmarketos.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