linux-kernel - Re: linux-next: build failure after merge of the drm-intel tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Wed, 27 Mar 2019 13:07:40 +0200
From:   Joonas Lahtinen <joonas.lahtinen@...ux.intel.com>
To:     DRI <dri-devel@...ts.freedesktop.org>,
        Daniel Vetter <daniel.vetter@...ll.ch>,
        Intel Graphics <intel-gfx@...ts.freedesktop.org>,
        Jani Nikula <jani.nikula@...ux.intel.com>,
        Rodrigo Vivi <rodrigo.vivi@...el.com>,
        Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Daniele Ceraolo Spurio <daniele.ceraolospurio@...el.com>,
        Paulo Zanoni <paulo.r.zanoni@...el.com>,
        Chris Wilson <chris@...is-wilson.co.uk>
Subject: Re: linux-next: build failure after merge of the drm-intel tree

Quoting Stephen Rothwell (2019-03-27 04:59:04)
> Hi all,
> 
> After merging the drm-intel tree, today's linux-next build (i386
> defconfig) failed like this:

We had a CI reporting mishap, where a failed 32-bit build resulted in
a misleading success e-mail being sent.

The tree is now fixed and we'll investigate the problem to avoid such
a false report in the future.

Regards, Joonas

> 
> In file included from drivers/gpu/drm/i915/intel_guc.h:28:0,
>                  from drivers/gpu/drm/i915/intel_uc.h:27,
>                  from drivers/gpu/drm/i915/intel_uc.c:25:
> drivers/gpu/drm/i915/intel_uncore.h: In function '__raw_uncore_read64':
> drivers/gpu/drm/i915/intel_uncore.h:257:9: error: implicit declaration of function 'readq'; did you mean 'readl'? [-Werror=implicit-function-declaration]
>   return read##s__(uncore->regs + i915_mmio_reg_offset(reg)); \
>          ^
> drivers/gpu/drm/i915/intel_uncore.h:269:1: note: in expansion of macro '__raw_read'
>  __raw_read(64, q)
>  ^~~~~~~~~~
> drivers/gpu/drm/i915/intel_uncore.h: In function '__raw_uncore_write64':
> drivers/gpu/drm/i915/intel_uncore.h:264:2: error: implicit declaration of function 'writeq'; did you mean 'writel'? [-Werror=implicit-function-declaration]
>   write##s__(val, uncore->regs + i915_mmio_reg_offset(reg)); \
>   ^
> drivers/gpu/drm/i915/intel_uncore.h:274:1: note: in expansion of macro '__raw_write'
>  __raw_write(64, q)
>  ^~~~~~~~~~~
> 
> Caused by commit
> 
>   6cc5ca768825 ("drm/i915: rename raw reg access functions")
> 
> I have reverted that commit and the following ones in the tree up to
> 
>   9511cb6481af ("drm/i915: Adding missing '; ' to ENGINE_INSTANCES")
> 
> -- 
> Cheers,
> Stephen Rothwell