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>,
Dmitry Baryshkov <lumag@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
Subject: Re: [PATCH 0/3] arm64: dts: qcom: sar2130p: correct display controller device
Date: Wed, 16 Jul 2025 14:40:51 -0500 [thread overview]
Message-ID: <175269485295.105136.4017202972666491272.b4-ty@kernel.org> (raw)
In-Reply-To: <20250618-sar2130p-fix-mdss-v1-0-78c2fb9e9fba@oss.qualcomm.com>
On Wed, 18 Jun 2025 20:49:50 +0300, Dmitry Baryshkov wrote:
> I didn't notice that Bjorn has picked up v1 of the SAR2130P display
> patchset instead of v5. Correct several mistakes that were fixed between
> those two versions.
>
>
Applied, thanks!
[1/3] arm64: dts: qcom: sar2130p: use TAG_ALWAYS for MDSS's mdp0-mem path
commit: 8d99dfc9c83c5a4b6f16f190dda7b6ed132530a1
[2/3] arm64: dts: qcom: sar2130p: correct VBIF region size for MDSS
commit: 6f49c8ab9137ceb5bbeed2a2fe9ab18c18ca025b
[3/3] arm64: dts: qcom: sar2130p: use defines for DSI PHY clocks
commit: 05bb4e8ef9ffc3c3b0ba19bc3d74f72e334a6d40
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2025-07-16 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-18 17:49 Dmitry Baryshkov
2025-06-18 17:49 ` [PATCH 1/3] arm64: dts: qcom: sar2130p: use TAG_ALWAYS for MDSS's mdp0-mem path Dmitry Baryshkov
2025-06-18 19:50 ` Konrad Dybcio
2025-06-18 17:49 ` [PATCH 2/3] arm64: dts: qcom: sar2130p: correct VBIF region size for MDSS Dmitry Baryshkov
2025-06-18 19:50 ` Konrad Dybcio
2025-06-18 17:49 ` [PATCH 3/3] arm64: dts: qcom: sar2130p: use defines for DSI PHY clocks Dmitry Baryshkov
2025-06-18 19:50 ` Konrad Dybcio
2025-07-16 19:40 ` 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=175269485295.105136.4017202972666491272.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=konrad.dybcio@oss.qualcomm.com \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@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®