From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Kishon Vijay Abraham I <kishon@ti.com>, Vinod Koul <vkoul@kernel.org>
Cc: Kuogee Hsieh <quic_khsieh@quicinc.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build failure after merge of the phy-next tree
Date: Thu, 7 Jul 2022 15:39:40 +1000 [thread overview]
Message-ID: <20220707153941.668cd6d5@canb.auug.org.au> (raw)
[-- Attachment #1: Type: text/plain, Size: 1044 bytes --]
Hi all,
After merging the phy-next tree, today's linux-next build (x86_64
allmodconfig) failed like this:
drivers/phy/qualcomm/phy-qcom-qmp-combo.c: In function 'qcom_qmp_phy_combo_vreg_init':
drivers/phy/qualcomm/phy-qcom-qmp-combo.c:2004:9: error: 'Return' undeclared (first use in this function)
2004 | Return 0;
| ^~~~~~
drivers/phy/qualcomm/phy-qcom-qmp-combo.c:2004:9: note: each undeclared identifier is reported only once for each function it appears in
drivers/phy/qualcomm/phy-qcom-qmp-combo.c:2004:15: error: expected ';' before numeric constant
2004 | Return 0;
| ^~
| ;
drivers/phy/qualcomm/phy-qcom-qmp-combo.c:2005:1: error: control reaches end of non-void function [-Werror=return-type]
2005 | }
| ^
cc1: all warnings being treated as errors
Caused by commit
6bd9a9be5d73 ("phy: qcom-qmp: add regulator_set_load to dp phy")
I have used the phy-next tree from next-20220706 for today.
--
Cheers,
Stephen Rothwell
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next reply other threads:[~2022-07-07 5:51 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 5:39 Stephen Rothwell [this message]
2022-07-07 5:53 ` linux-next: build failure after merge of the phy-next tree Vinod Koul
-- strict thread matches above, loose matches on Subject: below --
2023-08-18 5:40 Stephen Rothwell
2023-08-22 14:00 ` Vinod Koul
2023-02-13 2:55 Stephen Rothwell
2023-02-13 5:17 ` Vinod Koul
2023-02-13 5:17 ` Vinod Koul
2021-12-24 3:03 Stephen Rothwell
2021-12-24 4:37 ` Vinod Koul
2021-12-15 13:49 broonie
2021-12-15 14:14 ` Marcel Ziswiler
2021-12-15 15:20 ` Vinod Koul
2020-12-01 6:07 Stephen Rothwell
2020-12-01 6:45 ` Sergio Paracuellos
2020-12-01 10:39 ` Vinod Koul
2020-11-17 2:40 Stephen Rothwell
2020-11-17 10:00 ` Vinod Koul
2020-11-18 2:56 ` Stephen Rothwell
2020-11-18 4:23 ` Vinod Koul
2019-08-27 5:50 Stephen Rothwell
2017-03-30 3:47 Stephen Rothwell
2017-03-30 5:39 ` Kishon Vijay Abraham I
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=20220707153941.668cd6d5@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=kishon@ti.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=quic_khsieh@quicinc.com \
--cc=vkoul@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.