linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Daniel Vetter <daniel.vetter@ffwll.ch>,
	Intel Graphics <intel-gfx@lists.freedesktop.org>,
	DRI <dri-devel@lists.freedesktop.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Chris Wilson <chris@chris-wilson.co.uk>,
	Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Subject: linux-next: build failure after merge of the drm-intel tree
Date: Tue, 23 Aug 2016 11:56:14 +1000	[thread overview]
Message-ID: <20160823115614.3182f7db@canb.auug.org.au> (raw)

Hi all,

After merging the drm-intel tree, today's linux-next build (arm
multi_v7_defconfig) failed like this:

In file included from drivers/gpio/gpiolib-of.c:19:0:
include/linux/io-mapping.h:115:31: fatal error: asm/pgtable_types.h: No such file or directory
In file included from drivers/gpu/drm/nouveau/include/nvif/os.h:16:0,
                 from drivers/gpu/drm/nouveau/include/nvkm/core/os.h:3,
                 from drivers/gpu/drm/nouveau/include/nvkm/core/object.h:3,   
                 from drivers/gpu/drm/nouveau/include/nvkm/core/client.h:3,   
                 from drivers/gpu/drm/nouveau/nvkm/core/client.c:24:
include/linux/io-mapping.h:115:31: fatal error: asm/pgtable_types.h: No such file or directory

and many more.

Caused by commit

  cafaf14a5d8f ("io-mapping: Always create a struct to hold metadata about the io-mapping")

I have used the drm-intel tree from next-20160822 for today.

-- 
Cheers,
Stephen Rothwell

             reply	other threads:[~2016-08-23  1:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-23  1:56 Stephen Rothwell [this message]
2016-08-23 16:33 ` linux-next: build failure after merge of the drm-intel tree Daniel Vetter
  -- strict thread matches above, loose matches on Subject: below --
2022-08-26  2:36 Stephen Rothwell
2022-08-26  7:50 ` Jani Nikula
2022-04-26  2:08 Stephen Rothwell
2022-04-26  7:36 ` Jani Nikula
2022-02-15  1:10 Stephen Rothwell
2022-02-15 12:11 ` Jani Nikula
2021-05-21  1:58 Stephen Rothwell
2021-01-19 23:57 Stephen Rothwell
2021-01-21  1:11 ` Stephen Rothwell
     [not found] <20191210093957.5120f717@canb.auug.org.au>
     [not found] ` <20191210094224.4a294cb7@canb.auug.org.au>
2019-12-11  9:31   ` Jani Nikula
2019-03-27  2:59 Stephen Rothwell
2019-03-27 11:07 ` Joonas Lahtinen
2019-03-27 11:31   ` Stephen Rothwell
2018-07-13  1:54 Stephen Rothwell
2018-07-23  2:29 ` Stephen Rothwell
2018-05-08  1:07 Stephen Rothwell
2018-05-08  7:08 ` Oleksandr Andrushchenko
2018-05-09  5:02 ` Stephen Rothwell
2018-05-09  5:08   ` Christoph Hellwig
2018-05-09  5:18     ` Stephen Rothwell
2016-05-23  2:24 Stephen Rothwell
2014-04-03  1:24 Stephen Rothwell
2014-03-19  0:53 Stephen Rothwell
2014-03-19  1:18 ` Steven Rostedt
2013-02-15  2:37 Stephen Rothwell
2013-02-15  9:30 ` Daniel Vetter
2013-02-15 16:16   ` Jesse Barnes
2013-02-19  2:01     ` Stephen Rothwell
2013-02-19 10:28       ` 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=20160823115614.3182f7db@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=chris@chris-wilson.co.uk \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).