Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
Date:   Wed, 27 Apr 2022 10:48:25 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc:     Fabien Parent <fparent@baylibre.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 input tree
Message-ID: <20220427104825.15a04680@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/djBJ2_E+oJ90mkL9SpRNhZu";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/djBJ2_E+oJ90mkL9SpRNhZu
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

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

drivers/input/keyboard/mtk-pmic-keys.c:93:36: error: 'MT6359_TOPSTATUS' und=
eclared here (not in a function); did you mean 'MT6358_TOPSTATUS'?
   93 |                 MTK_PMIC_KEYS_REGS(MT6359_TOPSTATUS,
      |                                    ^~~~~~~~~~~~~~~~
drivers/input/keyboard/mtk-pmic-keys.c:48:35: note: in definition of macro =
'MTK_PMIC_KEYS_REGS'
   48 |         .deb_reg                =3D _deb_reg,             \
      |                                   ^~~~~~~~
drivers/input/keyboard/mtk-pmic-keys.c:98:25: error: 'MT6359_TOP_RST_MISC' =
undeclared here (not in a function); did you mean 'MT6358_TOP_RST_MISC'?
   98 |         .pmic_rst_reg =3D MT6359_TOP_RST_MISC,
      |                         ^~~~~~~~~~~~~~~~~~~
      |                         MT6358_TOP_RST_MISC

Caused by commit

  0f97adf64314 ("Input: mtk-pmic-keys - add support for MT6359")

I have used the input tree from next-20220426 for today.

--=20
Cheers,
Stephen Rothwell

--Sig_/djBJ2_E+oJ90mkL9SpRNhZu
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmJoktkACgkQAVBC80lX
0GxXDggAoRkJM8iK0vyIiHoZDSClWaAuuhUb4v48SE/X9c4PiikBf4xG7M7t0UKs
bgAAcFAEJRigXrTLKvIrTut+yZgtzyj0RXZC5eBtWnzuGuKl9ayU6h7YVZTX7/bQ
TWZgUbhLddAlUmp3OskQ9vKcWf2sAc0ubZv2gMPd8ccsJorcL2EhwehOhDXNzBM3
1sMeT3Dj385tH7nGrKKlzypxlX5F6JcOXvInDJ1ynENj8NszDehrpqAYPHNV5+c4
qzfafs/AyDBkUOHx+cRb7GXkSSFLwxkc4+0sGU5VYqtDcfxanjRvyDXqEs3PFj4v
xg+d2vPGr/qNOSYaJW4u+BMVwnRQbA==
=V2qk
-----END PGP SIGNATURE-----

--Sig_/djBJ2_E+oJ90mkL9SpRNhZu--