Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18;
Date:   Fri, 17 Jul 2020 17:16:34 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Linus Walleij <linus.walleij@linaro.org>
Cc:     Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Hanks Chen <hanks.chen@mediatek.com>,
        Andy Teng <andy.teng@mediatek.com>,
        Mars Cheng <mars.cheng@mediatek.com>
Subject: linux-next: build failure after merge of the pinctrl tree
Message-ID: <20200717171634.4b68472c@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/Ip=NXk1Hx7QoDwi+Gmdo.e2";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

--Sig_/Ip=NXk1Hx7QoDwi+Gmdo.e2
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

After merging the pinctrl tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/pinctrl/mediatek/pinctrl-mt6779.c:783:1: warning: data definition h=
as no type or storage class
  783 | arch_initcall(mt6779_pinctrl_init);
      | ^~~~~~~~~~~~~
drivers/pinctrl/mediatek/pinctrl-mt6779.c:783:1: error: type defaults to 'i=
nt' in declaration of 'arch_initcall' [-Werror=3Dimplicit-int]
drivers/pinctrl/mediatek/pinctrl-mt6779.c:783:1: warning: parameter names (=
without types) in function declaration
drivers/pinctrl/mediatek/pinctrl-mt6779.c:779:19: warning: 'mt6779_pinctrl_=
init' defined but not used [-Wunused-function]
  779 | static int __init mt6779_pinctrl_init(void)
      |                   ^~~~~~~~~~~~~~~~~~~

Caused by commit

  e6f744c6ad4f ("pinctrl: mediatek: add pinctrl support for MT6779 SoC")

Forgot to include module.h (since it is tristate in Kconfig) or init.h?

I used the pinctrl tree from next-20200716 for today.

--=20
Cheers,
Stephen Rothwell

--Sig_/Ip=NXk1Hx7QoDwi+Gmdo.e2
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAl8RUFIACgkQAVBC80lX
0GwW4Qf/U9+yRyzHbBgotPvNHdRVuVngKgRqwGRr2Q+biDGlpjacKUVLt9om0Jb0
Uaet6q5UsQHBBjopnZg3N4knmaIVCUHTsDLdG+wHnjOUHsHrhdpQlK1A188Yti0B
UuOGJnCAlKMuNUmZDKn9u4X+F66X/BMCh0izUUETjmuV6zPc+X2OUBOIgEL/P7Yq
VUwbkXn1DGrzIvoxyWqVkALk4kOkivO6u564MN3a0jtdFBf4rvnV0ab5H3K8ZYH7
+Gd1FPXFkZagPeLDsY884eg1f9pzv/yJ4GzrV063Zj5LYACXv/wQawtPy8oMY9GZ
lU+huz43csOde8EMBwdU1kS1JFZ6jw==
=wOdB
-----END PGP SIGNATURE-----

--Sig_/Ip=NXk1Hx7QoDwi+Gmdo.e2--