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:   Wed, 6 Jul 2022 11:55:29 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Mark Brown <broonie@kernel.org>,
        Liam Girdwood <lgirdwood@gmail.com>
Cc:     Amadeusz =?UTF-8?B?U8WCYXdpxYRza2k=?= 
        <amadeuszx.slawinski@linux.intel.com>,
        Cezary Rojewski <cezary.rojewski@intel.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 sound-asoc tree
Message-ID: <20220706115529.7deea289@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/VFzInB2RX5dS4iDcD.IhnYZ";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/VFzInB2RX5dS4iDcD.IhnYZ
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

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

sound/soc/intel/avs/boards/i2s_test.c: In function 'avs_i2s_test_probe':
sound/soc/intel/avs/boards/i2s_test.c:130:60: error: format '%ld' expects a=
rgument of type 'long int', but argument 4 has type 'int' [-Werror=3Dformat=
=3D]
  130 |         card->name =3D devm_kasprintf(dev, GFP_KERNEL, "ssp%ld-loop=
back", ssp_port);
      |                                                          ~~^       =
     ~~~~~~~~
      |                                                            |       =
     |
      |                                                            long int=
     int
      |                                                          %d
cc1: all warnings being treated as errors

Caused by commit

  e39acc4cfd92 ("ASoC: Intel: avs: Add I2S-test machine board")

I have used the sound-asoc tree from next-20220705 for today.

--=20
Cheers,
Stephen Rothwell

--Sig_/VFzInB2RX5dS4iDcD.IhnYZ
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmLE65EACgkQAVBC80lX
0GzS0Af/YSwIFMvvWYfFz6A4lqsFBy75/UVdGQ/xGjEej28WnHpTsiLLvOHIu/xg
3DOGtdk3Hk0ze3XeV/b1w4xovV/qIb2maCFPxqxHCsxDPGP8QvjyKI20FxzuJhyi
XvDVDcAYgjKCZ0ub/v5x8xGzS57j4friorhPDjVZ9RYb2ZdPmJrGMrviLVCT2t0+
d1eIHYFxkF4/SW/psM3J86B/uw61uHl/cP6XjOcgxUiJaKjNU1zwjND1IH5sye1K
jhQX5NJ4NoUYsusxvJ3oDYiryPERNhKPsBSyxwWsOawbjWZZ1yR6TmStZe5ymf5u
/FNdcxVmtyWmw1Ea6xLFpvpI85fPjg==
=ByeV
-----END PGP SIGNATURE-----

--Sig_/VFzInB2RX5dS4iDcD.IhnYZ--