From: Sumit Garg <sumit.garg@kernel.org>
To: Tom Rini <trini@konsulko.com>,
Casey Connolly <casey.connolly@linaro.org>
Cc: u-boot@lists.denx.de, u-boot-qcom@groups.io,
neil.armstrong@linaro.org, Ajit Singh <blfizzyy@gmail.com>,
Antony Kurniawan Soemardi <linux@smankusors.com>,
Aswin Murugan <aswin.murugan@oss.qualcomm.com>,
Balaji Selvanathan <balaji.selvanathan@oss.qualcomm.com>,
Luca Weiss <luca.weiss@fairphone.com>,
Sumit Garg <sumit.garg@oss.qualcomm.com>,
Varadarajan Narayanan <varadarajan.narayanan@oss.qualcomm.com>
Subject: Re: [PULL] Please pull casey/qcom-main-13Apr2026
Date: Mon, 27 Apr 2026 12:29:43 +0530 [thread overview]
Message-ID: <ae8JX1O7PGJaFSX8@sumit-xelite> (raw)
In-Reply-To: <20260419154026.GV41863@bill-the-cat>
Hi Casey,
On Sun, Apr 19, 2026 at 09:40:26AM -0600, Tom Rini wrote:
> On Sun, Apr 19, 2026 at 05:03:16AM +0200, Casey Connolly wrote:
>
> > Hi Tom,
> >
> > Various Qualcomm additions this cycle:
> > * USB superspeed support for 1 platform
> > * Initial support for the Milos platform and the Fairphone Gen 6 (chainloaded from ABL)
> > * Improved support for booting with OP-TEE on supported platforms
> > * Initial basic power domain support
> >
> > Notably there is a generic change to the device core, missing power
> > domains will no longer cause a device to fail probe and instead will
> > just print a warning. This shouldn't affect any existing platforms.
>
> Unfortunately I get a fail to build in CI:
> https://source.denx.de/u-boot/u-boot/-/jobs/1428016
> +(qcm6490) drivers/phy/qcom/phy-qcom-qmp-combo.c: In function 'qmp_combo_com_init':
> +(qcm6490) drivers/phy/qcom/phy-qcom-qmp-combo.c:288:35: error: unused variable 'cfg' [-Werro
> r=unused-variable]
> +(qcm6490) 288 | const struct qmp_phy_cfg *cfg = qmp->cfg;
> +(qcm6490) | ^~~
> +(qcm6490) cc1: all warnings being treated as errors
> +(qcm6490) make[4]: *** [scripts/Makefile.build:271: drivers/phy/qcom/phy-qcom-qmp-combo.o] E
> rror 1
> +(qcm6490) make[3]: *** [scripts/Makefile.build:492: drivers/phy/qcom] Error 2
> +(qcm6490) make[2]: *** [scripts/Makefile.build:492: drivers/phy] Error 2
> +(qcm6490) make[1]: *** [Makefile:2205: drivers] Error 2
Do you plan to re-send this PR with updated USB super speed patch-set
from Balaji here [1] which should take care of this CI issue?
Since the v2026.04-rc1 is going to be tagged today, we really don't want
to miss this merge window again for all these pending features to be
merged.
[1] https://lore.kernel.org/all/20260418-kodiak_ss-v4-0-d381670c9d78@oss.qualcomm.com/
-Sumit
next prev parent reply other threads:[~2026-04-27 6:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-19 3:03 [PULL] Please pull casey/qcom-main-13Apr2026 Casey Connolly
2026-04-19 15:40 ` Tom Rini
2026-04-27 6:59 ` Sumit Garg [this message]
2026-04-27 10:30 ` Casey Connolly
2026-04-27 10:55 ` Sumit Garg
-- strict thread matches above, loose matches on Subject: below --
2026-04-27 11:46 Casey Connolly
2026-04-27 15:42 ` Tom Rini
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=ae8JX1O7PGJaFSX8@sumit-xelite \
--to=sumit.garg@kernel.org \
--cc=aswin.murugan@oss.qualcomm.com \
--cc=balaji.selvanathan@oss.qualcomm.com \
--cc=blfizzyy@gmail.com \
--cc=casey.connolly@linaro.org \
--cc=linux@smankusors.com \
--cc=luca.weiss@fairphone.com \
--cc=neil.armstrong@linaro.org \
--cc=sumit.garg@oss.qualcomm.com \
--cc=trini@konsulko.com \
--cc=u-boot-qcom@groups.io \
--cc=u-boot@lists.denx.de \
--cc=varadarajan.narayanan@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