Devicetree
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Esteban Urrutia <esteuwu@proton.me>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
	Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Subject: Re: [PATCH v2 0/2] SM8450 QoL changes (dts)
Date: Fri, 17 Jul 2026 23:04:20 +0200	[thread overview]
Message-ID: <88a87da7-ffa0-4f34-aba8-e8aa995aa79f@ixit.cz> (raw)
In-Reply-To: <178425854592.1084804.16144771627314071470.b4-ty@kernel.org>

On 17/07/2026 05:23, Bjorn Andersson wrote:
> 
> On Sat, 11 Jul 2026 23:12:26 -0400, Esteban Urrutia wrote:
>> These patches focus on correcting some details on the DTS for the SM8450
>> SoC.
>>
>>
> 
> Applied, thanks!
> 
> [1/2] arm64: dts: qcom: sm8450: Remove unneeded reserved memory nodes
>        commit: 0ed8261e0ebdac5f1f08dcbfc209efe36937ed2d
> [2/2] arm64: dts: qcom: sm8450: Add mode-switch property to qmpphy
>        commit: 8a2b4481b66c802af293e55eee07406971d5aa7b
> 
> Best regards,

I'm afraid there is v3 of this patchset :(

https://lore.kernel.org/all/20260713-sm8450-qol-dispcc-v3-0-56fd05822270@proton.me/

David

      reply	other threads:[~2026-07-17 21:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-12  3:12 [PATCH v2 0/2] SM8450 QoL changes (dts) Esteban Urrutia via B4 Relay
2026-07-12  3:12 ` [PATCH v2 1/2] arm64: dts: qcom: sm8450: Remove unneeded reserved memory nodes Esteban Urrutia via B4 Relay
2026-07-13 10:45   ` Konrad Dybcio
2026-07-12  3:12 ` [PATCH v2 2/2] arm64: dts: qcom: sm8450: Add mode-switch property to qmpphy Esteban Urrutia via B4 Relay
2026-07-13 10:45   ` Konrad Dybcio
2026-07-17  3:23 ` [PATCH v2 0/2] SM8450 QoL changes (dts) Bjorn Andersson
2026-07-17 21:04   ` David Heidelberg [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=88a87da7-ffa0-4f34-aba8-e8aa995aa79f@ixit.cz \
    --to=david@ixit.cz \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@oss.qualcomm.com \
    --cc=esteuwu@proton.me \
    --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