Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Thu, 7 Jul 2022 15:39:40 +1000
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
Message-ID: <20220707153941.668cd6d5@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/hXdHKrv=JBiP0DAOAy4IOBz";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/hXdHKrv=JBiP0DAOAy4IOBz
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

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' undeclare=
d (first use in this function)
 2004 |         Return 0;
      |         ^~~~~~
drivers/phy/qualcomm/phy-qcom-qmp-combo.c:2004:9: note: each undeclared ide=
ntifier is reported only once for each function it appears in
drivers/phy/qualcomm/phy-qcom-qmp-combo.c:2004:15: error: expected ';' befo=
re numeric constant
 2004 |         Return 0;
      |               ^~
      |               ;
drivers/phy/qualcomm/phy-qcom-qmp-combo.c:2005:1: error: control reaches en=
d of non-void function [-Werror=3Dreturn-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.

--=20
Cheers,
Stephen Rothwell

--Sig_/hXdHKrv=JBiP0DAOAy4IOBz
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmLGcZ0ACgkQAVBC80lX
0GwG+wf9Es2SHRQKBPZh9aMsmTol3LYUzu0T6EkF/k4fC2WDXfOBH2u6N+FATLI3
CEWsdG+BAyTQQ7qQBYCSi7h4hJtNz3Kg7IW6j2nnMcb1w7PGdnSk87amiTW4Dy+s
tWgnrO5DBMJvBGJeuIR0PjYtgfdwyHGceCXBulV7+X9anxeeKvJq/WSWwwFslHME
SCMsxuvbcye+8dVgQdw3U8/pYum73P5M41HNlVkpq84ZOUa4lkFWHxwIBxthNiUx
5d/bn8XOYTVvGMA4m4bx/sMaV63Btzr1BimlyGfd+CkWM+LTHEysL7j9EbSt3w6y
yF1BP16QnqSErlhaZnBw88X1C4tRwg==
=iJLV
-----END PGP SIGNATURE-----

--Sig_/hXdHKrv=JBiP0DAOAy4IOBz--