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:   Tue, 15 Feb 2022 12:10:39 +1100
From:   Stephen Rothwell <sfr@canb.auug.org.au>
To:     Daniel Vetter <daniel.vetter@ffwll.ch>,
        Jani Nikula <jani.nikula@linux.intel.com>,
        Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
        Rodrigo Vivi <rodrigo.vivi@intel.com>,
        Intel Graphics <intel-gfx@lists.freedesktop.org>,
        DRI <dri-devel@lists.freedesktop.org>
Cc:     Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Linux Next Mailing List <linux-next@vger.kernel.org>,
        Dave Airlie <airlied@linux.ie>
Subject: linux-next: build failure after merge of the drm-intel tree
Message-ID: <20220215121039.1d1ec3e6@canb.auug.org.au>
MIME-Version: 1.0
Content-Type: multipart/signed; boundary="Sig_/iNPkmkrXrHfJuuRrqT7jTy7";
 protocol="application/pgp-signature"; micalg=pgp-sha256
Precedence: bulk

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

Hi all,

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

drivers/gpu/drm/i915/gvt/kvmgt.c: In function 'handle_edid_regs':
drivers/gpu/drm/i915/gvt/kvmgt.c:595:38: error: implicit declaration of fun=
ction 'drm_edid_block_valid' [-Werror=3Dimplicit-function-declaration]
  595 |                                 if (!drm_edid_block_valid(
      |                                      ^~~~~~~~~~~~~~~~~~~~

Presumably caused by commit

  14da21cc4671 ("drm/i915: axe lots of unnecessary includes from i915_drv.h=
")

I am beginning to wonder if you guys run stuff through your CI before
relasing to linux-next.  Especially important when removing #include
statements from include files :-)

I have used the drm-intel tree from next-20220214 for today.

--=20
Cheers,
Stephen Rothwell

--Sig_/iNPkmkrXrHfJuuRrqT7jTy7
Content-Type: application/pgp-signature
Content-Description: OpenPGP digital signature

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

iQEzBAEBCAAdFiEENIC96giZ81tWdLgKAVBC80lX0GwFAmIK/Y8ACgkQAVBC80lX
0GzcTQf+LTxs6K5vvlhHDFfi9sLywA62S26SiPukd5M8LQmFQUfrnS3k84wRNyaf
ljDaUrdT1TxCmk4STGKGYq+jaYCHlt7fVwA2Cps5F7BSYibeGWLaBdEvNdfn0CFE
3ycP7KLf7c3cdY5ks2MU+d/vKhTm0s/wtFcXzFJ6zrXxnUXakL0EJ2PPh/WaIlna
r4mNbGMyhvK+SAZQ4sBo77m+KK6RN6f/Mh7qwpHI1UBL6lrOwiTltwlUkoJFT8xT
O7o/eh13cvuGAcMWxHHPfV95YNgp7gf2zpYGDlSE0s6r2NO0b80LHPRjrThVxKuk
byH3Zfrkz51IxRX6upG3kJSErt68TA==
=rp64
-----END PGP SIGNATURE-----

--Sig_/iNPkmkrXrHfJuuRrqT7jTy7--