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:   Mon, 5 Jun 2023 08:58:16 +1000
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Hector Martin <marcan@marcan.st>
Cc:     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 asahi-soc tree
Message-ID: <20230605085816.4f54bb43@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/MEfKpnWJCz/ikhWn.0qA1Ks";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

--Sig_/MEfKpnWJCz/ikhWn.0qA1Ks
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

Hi all,

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

In file included from include/linux/io.h:13,
                 from drivers/soc/apple/mailbox.c:22:
drivers/soc/apple/mailbox.c: In function 'apple_mbox_send':
drivers/soc/apple/mailbox.c:151:24: error: implicit declaration of function=
 'FIELD_PREP' [-Werror=3Dimplicit-function-declaration]
  151 |         writeq_relaxed(FIELD_PREP(APPLE_MBOX_MSG1_MSG, msg.msg1),
      |                        ^~~~~~~~~~
arch/x86/include/asm/io.h:103:42: note: in definition of macro 'writeq_rela=
xed'
  103 | #define writeq_relaxed(v, a)    __writeq(v, a)
      |                                          ^
drivers/soc/apple/mailbox.c: In function 'apple_mbox_poll_locked':
drivers/soc/apple/mailbox.c:188:28: error: implicit declaration of function=
 'FIELD_GET' [-Werror=3Dimplicit-function-declaration]
  188 |                 msg.msg1 =3D FIELD_GET(
      |                            ^~~~~~~~~

Caused by commit

  0d1f3f7f8486 ("soc: apple: mailbox: Add ASC/M3 mailbox driver")

I have used the asshi-soc tree from next-20230602 for today.

--=20
Cheers,
Stephen Rothwell

--Sig_/MEfKpnWJCz/ikhWn.0qA1Ks
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmR9FwgACgkQAVBC80lX
0GzT7gf7BejVMP1/O2HFhoj1kF5QNrpKOwGzkhv0rNvJJudC5EwubRjdJbSjQmn2
gpm/M6HB9KDO4P/eeA4yt4LVFVgkC0V8xqEDdQVhPsRAm8dJh1FBzYHhb5RHEikP
bqIr0By7ZWYzkSk6xmMTwjzuobnhFvwU5o+sVcttx2cdYWkJ7Ap1BAYx8VK/iuGw
h0TuILt/sc8+XY11nSciLubQLwnski4Np/0trVMz2lSde+j/Sv13jlApgub5aKqh
sfEM9rWoN0nITrs7Aamhfhy/dyFCMfRIv+WUnzyTH3HVaNCFJsT6MdOCazuTnHfY
jbdVZmMWmgQeSp920JauLqZQtenJlg==
=d5QJ
-----END PGP SIGNATURE-----

--Sig_/MEfKpnWJCz/ikhWn.0qA1Ks--