From: Esteban Urrutia <esteuwu@proton.me>
To: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Brian Masney <bmasney@redhat.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Jagadeesh Kona <quic_jkona@quicinc.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, phone-devel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH v3 0/3] SM8450 QoL changes (dispcc)
Date: Mon, 10 Aug 2026 16:31:37 +0000 [thread overview]
Message-ID: <aa71663e-103b-4f61-affd-e3a35a1690bd@proton.me> (raw)
In-Reply-To: <20260713-sm8450-qol-dispcc-v3-0-56fd05822270@proton.me>
On 7/13/26 11:28 PM, Esteban Urrutia via B4 Relay wrote:
> These patches are mainly focused on getting a flickerless boot process
> on SM8475 based devices.
Any update on when this series can be picked?
Regards,
Esteban
next prev parent reply other threads:[~2026-08-10 16:31 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-14 3:28 [PATCH v3 0/3] SM8450 QoL changes (dispcc) Esteban Urrutia
2026-07-14 3:28 ` Esteban Urrutia via B4 Relay
2026-07-14 3:28 ` [PATCH v3 1/3] clk: qcom: dispcc-sm8450: Fix disp_cc_mdss_mdp_clk_src ops Esteban Urrutia
2026-07-14 3:28 ` Esteban Urrutia via B4 Relay
2026-07-17 21:02 ` David Heidelberg
2026-07-18 23:28 ` Esteban Urrutia
2026-07-20 8:14 ` Konrad Dybcio
2026-07-22 13:23 ` Dmitry Baryshkov
2026-07-14 3:28 ` [PATCH v3 2/3] clk: qcom: dispcc-sm8450: Migrate to qcom_cc_driver_data Esteban Urrutia
2026-07-14 3:28 ` Esteban Urrutia via B4 Relay
2026-07-22 13:24 ` Dmitry Baryshkov
2026-07-14 3:28 ` [PATCH v3 3/3] clk: qcom: alpha-pll: Check Lucid Ole PLL status before configuring Esteban Urrutia
2026-07-14 3:28 ` Esteban Urrutia via B4 Relay
2026-07-15 9:31 ` Konrad Dybcio
2026-07-29 2:44 ` Esteban Urrutia
2026-07-29 9:24 ` Konrad Dybcio
2026-08-10 16:31 ` Esteban Urrutia [this message]
2026-08-10 18:45 ` [PATCH v3 0/3] SM8450 QoL changes (dispcc) Bjorn Andersson
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=aa71663e-103b-4f61-affd-e3a35a1690bd@proton.me \
--to=esteuwu@proton.me \
--cc=andersson@kernel.org \
--cc=bmasney@redhat.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=mturquette@baylibre.com \
--cc=phone-devel@vger.kernel.org \
--cc=quic_jkona@quicinc.com \
--cc=sboyd@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.