From: Krzysztof Kozlowski <krzk@kernel.org>
To: Val Packett <val@packett.cool>
Cc: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
Martin Botka <martin.botka@somainline.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/6] clk: qcom: dispcc-sm6125: Add missing MDSS resets
Date: Tue, 17 Feb 2026 09:12:17 +0100 [thread overview]
Message-ID: <20260217-purring-ubiquitous-starfish-dfcabb@quoll> (raw)
In-Reply-To: <20260216233600.13098-6-val@packett.cool>
On Mon, Feb 16, 2026 at 08:25:22PM -0300, Val Packett wrote:
> The MDSS resets were left undescribed, fix that.
Fix what? It is perfectly fine to have things "undescribed". Explain
what is the problem of these being missing.
>
> Fixes: 6e87c8f07407 ("clk: qcom: Add display clock controller driver for SM6125")
> Signed-off-by: Val Packett <val@packett.cool>
> ---
> drivers/clk/qcom/dispcc-sm6125.c | 7 +++++++
> 1 file changed, 7 insertions(+)
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-02-17 8:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 23:25 [PATCH 0/6] SM6115/SM6125 MDSS core reset Val Packett
2026-02-16 23:25 ` [PATCH 1/6] dt-bindings: clock: qcom,sm6115-dispcc: Define MDSS resets Val Packett
2026-02-17 8:11 ` Krzysztof Kozlowski
2026-02-16 23:25 ` [PATCH 2/6] dt-bindings: clock: qcom,dispcc-sm6125: " Val Packett
2026-02-16 23:25 ` [PATCH 3/6] clk: qcom: dispcc-sm6115: Add missing " Val Packett
2026-02-17 7:36 ` Dmitry Baryshkov
2026-02-17 9:22 ` Konrad Dybcio
2026-02-16 23:25 ` [PATCH 4/6] clk: qcom: dispcc-sm6125: " Val Packett
2026-02-17 7:37 ` Dmitry Baryshkov
2026-02-17 8:12 ` Krzysztof Kozlowski [this message]
2026-02-17 9:22 ` Konrad Dybcio
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=20260217-purring-ubiquitous-starfish-dfcabb@quoll \
--to=krzk@kernel.org \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=martin.botka@somainline.org \
--cc=mturquette@baylibre.com \
--cc=phone-devel@vger.kernel.org \
--cc=sboyd@kernel.org \
--cc=val@packett.cool \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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