From: Randy Dunlap <rdunlap@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Linux-Next Mailing List <linux-next@vger.kernel.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>
Subject: Re: linux-next: Tree for Sep 19 (drivers/gpu/drm/i915/i915_gem.c)
Date: Tue, 19 Sep 2017 08:49:36 -0700 [thread overview]
Message-ID: <537cae4b-0157-85da-2a47-a768e34eb412@infradead.org> (raw)
In-Reply-To: <20170919141557.03ffb2a7@canb.auug.org.au>
On 09/18/17 21:15, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20170918:
>
> Linus' tree still had its build failure for which I reverted a commit.
>
> The drm-intel tree gained conflicts against Linus' tree.
>
on x86_64:
In file included from ../drivers/gpu/drm/i915/i915_gem.c:5342:0:
../drivers/gpu/drm/i915/selftests/mock_gem_device.c: In function 'mock_gem_device':
../drivers/gpu/drm/i915/selftests/mock_gem_device.c:150:20: error: 'struct dev_archdata' has no member named 'iommu'
pdev->dev.archdata.iommu = (void *)-1;
^
when IOMMU_SUPPORT, INTEL_IOMMU, and AMD_IOMMU are not enabled.
struct dev_archdata {
#if defined(CONFIG_INTEL_IOMMU) || defined(CONFIG_AMD_IOMMU)
void *iommu; /* hook for IOMMU specific extension */
#endif
};
--
~Randy
next prev parent reply other threads:[~2017-09-19 15:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 4:15 linux-next: Tree for Sep 19 Stephen Rothwell
2017-09-19 15:49 ` Randy Dunlap [this message]
2017-09-19 15:54 ` linux-next: Tree for Sep 19 (x86/kernel/cpuinfo.c) Randy Dunlap
2017-09-26 1:19 ` Randy Dunlap
2017-09-26 7:40 ` Thomas Gleixner
2017-09-26 8:18 ` Greg Kroah-Hartman
2017-09-26 10:40 ` Thomas Gleixner
2017-09-26 12:36 ` Felix Schnizlein
2017-09-26 16:00 ` Thomas Gleixner
2017-09-26 21:18 ` Greg Kroah-Hartman
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=537cae4b-0157-85da-2a47-a768e34eb412@infradead.org \
--to=rdunlap@infradead.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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
all inboxes | Powered by JetHome®