Hi Daniel, [auto build test ERROR on drm/drm-next] [also build test ERROR on next-20170503] [cannot apply to v4.11] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Daniel-Vetter/vblanke-cleanup-resend/20170504-003948 base: git://people.freedesktop.org/~airlied/linux.git drm-next config: arm-allmodconfig (attached as .config) compiler: arm-linux-gnueabi-gcc (Debian 6.1.1-9) 6.1.1 20160705 reproduce: wget https://raw.githubusercontent.com/01org/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross # save the attached .config to linux build tree make.cross ARCH=arm Note: the linux-review/Daniel-Vetter/vblanke-cleanup-resend/20170504-003948 HEAD 7d42e23d7949707be44be8720a9eb260534aa4dc builds fine. It only hurts bisectibility. All errors (new ones prefixed by >>): drivers/gpu//drm/vc4/vc4_crtc.c: In function 'vc4_crtc_get_scanoutpos': >> drivers/gpu//drm/vc4/vc4_crtc.c:235:6: error: 'in_vblank_irq' undeclared (first use in this function) if (in_vblank_irq) { ^~~~~~~~~~~~~ drivers/gpu//drm/vc4/vc4_crtc.c:235:6: note: each undeclared identifier is reported only once for each function it appears in vim +/in_vblank_irq +235 drivers/gpu//drm/vc4/vc4_crtc.c 229 * We can't get meaningful readings wrt. scanline position of the PV 230 * and need to make things up in a approximative but consistent way. 231 */ 232 ret |= DRM_SCANOUTPOS_IN_VBLANK; 233 vblank_lines = mode->vtotal - mode->vdisplay; 234 > 235 if (in_vblank_irq) { 236 /* 237 * Assume the irq handler got called close to first 238 * line of vblank, so PV has about a full vblank --- 0-DAY kernel test infrastructure Open Source Technology Center https://lists.01.org/pipermail/kbuild-all Intel Corporation
Attachment:
.config.gz
Description: application/gzip
_______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/intel-gfx
