Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8BIT
To:     DRI <dri-devel@lists.freedesktop.org>,
        Daniel Vetter <daniel.vetter@ffwll.ch>,
        Intel Graphics <intel-gfx@lists.freedesktop.org>,
        Jani Nikula <jani.nikula@linux.intel.com>,
        Rodrigo Vivi <rodrigo.vivi@intel.com>,
        Stephen Rothwell <sfr@canb.auug.org.au>
From:   Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo
In-Reply-To: <20190327135904.7830c60c@canb.auug.org.au>
Cc:     Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>,
        Paulo Zanoni <paulo.r.zanoni@intel.com>,
        Chris Wilson <chris@chris-wilson.co.uk>
References: <20190327135904.7830c60c@canb.auug.org.au>
Message-ID: <155368485987.8699.12849690159482129286@jlahtine-desk.ger.corp.intel.com>
User-Agent: alot/0.7
Subject: Re: linux-next: build failure after merge of the drm-intel tree
Date:   Wed, 27 Mar 2019 13:07:40 +0200
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

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