[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87r1845ny4.fsf@intel.com>
Date: Tue, 15 Feb 2022 14:11:47 +0200
From: Jani Nikula <jani.nikula@...ux.intel.com>
To: Stephen Rothwell <sfr@...b.auug.org.au>,
Daniel Vetter <daniel.vetter@...ll.ch>,
Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>,
Rodrigo Vivi <rodrigo.vivi@...el.com>,
Intel Graphics <intel-gfx@...ts.freedesktop.org>,
DRI <dri-devel@...ts.freedesktop.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Dave Airlie <airlied@...ux.ie>
Subject: Re: linux-next: build failure after merge of the drm-intel tree
On Tue, 15 Feb 2022, Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 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 function 'drm_edid_block_valid' [-Werror=implicit-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 :-)
Thanks for the report. Apparently CI (and I) have VFIO=n, VFIO_MDEV=n,
and DRM_I915_GVT_KVMGT=n.
BR,
Jani.
>
> I have used the drm-intel tree from next-20220214 for today.
--
Jani Nikula, Intel Open Source Graphics Center
Powered by blists - more mailing lists