From: Jason Pettit <jason.pettit@oss.qualcomm.com>
To: Nabige Aala <nabige.aala@oss.qualcomm.com>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Wesley Cheng <wesley.cheng@oss.qualcomm.com>,
Abel Vesa <abelvesa@kernel.org>,
Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Jason Pettit <jason.pettit@oss.qualcomm.com>,
Ritesh Kumar <ritesh.kumar@oss.qualcomm.com>,
Mahadevan P <mahadevan.p@oss.qualcomm.com>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: qualcomm: qmp-combo: update DP PHY PLL programming on Glymur
Date: Sat, 22 Aug 2026 07:25:08 -0700 [thread overview]
Message-ID: <20260822142508.25473-1-jason.pettit@oss.qualcomm.com> (raw)
In-Reply-To: <20260721-glymur-phy-conf-v1-1-7c8909552c5e@oss.qualcomm.com>
On Tue, Jul 21, 2026 at 10:48:33AM +0530, Nabige Aala wrote:
> +#include "phy-qcom-qmp-dp-qserdes-com-v8.h"
That filename does not match the one accepted upstream. In Linus' tree the
header is
drivers/phy/qualcomm/phy-qcom-qmp-qserdes-dp-com-v8.h
The "dp" and "qserdes" components are transposed. As written the build stops
at the include.
drivers/phy/qualcomm/phy-qcom-qmp-combo.c:56:10: fatal error:
phy-qcom-qmp-dp-qserdes-com-v8.h: No such file or directory
Dropping the line instead is not a fix, because the patch uses two symbols the
header supplies.
phy-qcom-qmp-combo.c:321: error: 'DP_QSERDES_V8_COM_C_READY_STATUS' undeclared
phy-qcom-qmp-combo.c:322: error: 'DP_QSERDES_V8_COM_CMN_STATUS' undeclared
Both are defined in phy-qcom-qmp-qserdes-dp-com-v8.h, which has been present in
mainline since v7.0-rc1. Correcting the spelling is the only change needed. With
that one edit the patch builds cleanly for me on next-20260821.
One other thing for the respin. The patch no longer applies with a plain git am
on current linux-next. The include block gained a line in
eca0e717aab1 ("phy: qualcomm: qmp-combo: Add support for Hawi SoC")
so the context of the first hunk no longer matches. git am -3 applies it.
One process note. The subject line reads [PATCH], but the changelog in this
message reads "Changes in v2". The revision is therefore invisible to b4, to
patchwork, and to anyone following the thread. When you split this into the
smaller commits Dmitry asked for, please post the result as
[PATCH v3 0/3]
rather than starting the numbering again from [PATCH]. That keeps the lineage
traceable from v1 through the split series.
I am carrying this patch as a prerequisite for HP EliteBook X G2q board support,
so I am happy to test a v2 on Glymur hardware.
Thanks,
Jason
next prev parent reply other threads:[~2026-08-22 14:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-21 5:18 Nabige Aala
2026-07-21 23:26 ` Dmitry Baryshkov
2026-08-21 6:04 ` Nabige Aala
2026-08-22 14:25 ` Jason Pettit [this message]
2026-08-24 1:41 ` Jason Pettit
2026-08-24 5:59 ` Nabige Aala
-- strict thread matches above, loose matches on Subject: below --
2026-04-19 10:15 Mahadevan P
2026-04-19 13:18 ` Dmitry Baryshkov
2026-04-20 14:18 ` Mahadevan P
2026-04-22 9:54 ` Konrad Dybcio
2026-04-22 15:40 ` Dmitry Baryshkov
2026-04-22 9:36 ` Konrad Dybcio
2026-04-22 10:06 ` 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=20260822142508.25473-1-jason.pettit@oss.qualcomm.com \
--to=jason.pettit@oss.qualcomm.com \
--cc=abelvesa@kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=mahadevan.p@oss.qualcomm.com \
--cc=nabige.aala@oss.qualcomm.com \
--cc=neil.armstrong@linaro.org \
--cc=ritesh.kumar@oss.qualcomm.com \
--cc=vkoul@kernel.org \
--cc=wesley.cheng@oss.qualcomm.com \
/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®