From: Mark Brown <broonie@kernel•org>
To: Daniel Vetter <daniel.vetter@ffwll•ch>,
Intel Graphics <intel-gfx@lists•freedesktop.org>,
DRI <dri-devel@lists•freedesktop.org>,
Chris Wilson <chris@chris-wilson•co.uk>,
Joonas Lahtinen <joonas.lahtinen@linux•intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel•com>
Cc: Linux-Next Mailing List <linux-next@vger•kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger•kernel.org>
Subject: Re: linux-next: build failure after merge of the drm-intel-fixes tree
Date: Wed, 11 Oct 2017 09:51:06 +0100 [thread overview]
Message-ID: <20171011085106.cusi65s2du3n537y@sirena.co.uk> (raw)
In-Reply-To: <20171010070300.6fsdy52752resxqn@sirena.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]
On Tue, Oct 10, 2017 at 08:03:00AM +0100, Mark Brown wrote:
> Hi all,
>
> After merging the drm-misc-fixes tree, today's linux-next build
> (x86_allmodconfig) failed like this:
>
> CC [M] drivers/gpu/drm/i915/i915_gem_evict.o
> drivers/gpu/drm/i915/i915_gem_evict.c: In function ‘i915_gem_evict_for_node’:
> drivers/gpu/drm/i915/i915_gem_evict.c:318:31: error: implicit declaration of function ‘i915_vma_has_userfault’; did you mean ‘i915_vma_pin_count’? [-Werror=implicit-function-declaration]
> if (flags & PIN_NONFAULT && i915_vma_has_userfault(vma)) {
> ^~~~~~~~~~~~~~~~~~~~~~
> i915_vma_pin_count
>
> Caused by commit
>
> 72872c99b6dbc ("drm/i915: Check PIN_NONFAULT overlaps in evict_for_node")
>
> in the drm-intel-fixes tree. I've used the tree from yesterday.
This is still present today.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists•freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-11 8:51 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-10 7:03 linux-next: build failure after merge of the drm-intel-fixes tree Mark Brown
2017-10-11 8:51 ` Mark Brown [this message]
2017-10-11 17:39 ` [Intel-gfx] " Rodrigo Vivi
-- strict thread matches above, loose matches on Subject: below --
2022-07-13 12:14 Stephen Rothwell
2022-01-31 22:27 Stephen Rothwell
2020-11-03 22:37 Stephen Rothwell
2020-11-04 0:25 ` Rodrigo Vivi
2020-06-15 23:39 Stephen Rothwell
2020-06-16 9:22 ` Joonas Lahtinen
2020-05-28 22:30 Stephen Rothwell
2020-01-20 21:34 Stephen Rothwell
2020-01-21 7:13 ` Joonas Lahtinen
2019-01-29 22:39 Stephen Rothwell
2019-01-29 22:53 ` Lucas De Marchi
2019-01-30 8:22 ` Jani Nikula
2018-05-29 9:26 Stephen Rothwell
2018-05-29 11:45 ` Joonas Lahtinen
2017-01-02 23:42 Stephen Rothwell
2017-01-03 2:59 ` Zhenyu Wang
2017-01-03 4:07 ` Stephen Rothwell
2017-01-03 4:48 ` Alex Williamson
2017-01-03 9:23 ` Zhenyu Wang
2017-01-03 13:25 ` Jani Nikula
2017-01-03 20:37 ` Alex Williamson
2017-01-04 9:07 ` Daniel Vetter
2014-06-06 2:03 Stephen Rothwell
2014-06-06 6:45 ` Daniel Vetter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171011085106.cusi65s2du3n537y@sirena.co.uk \
--to=broonie@kernel$(echo .)org \
--cc=chris@chris-wilson$(echo .)co.uk \
--cc=daniel.vetter@ffwll$(echo .)ch \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=intel-gfx@lists$(echo .)freedesktop.org \
--cc=joonas.lahtinen@linux$(echo .)intel.com \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=rodrigo.vivi@intel$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox