From: Ingo Molnar <mingo@elte.hu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Avi Kivity <avi@qumranet.com>,
linux-next@vger.kernel.org,
Suresh Siddha <suresh.b.siddha@intel.com>,
"Kay, Allen M" <allen.m.kay@intel.com>,
Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: linux-next: kvm tree build failure
Date: Wed, 17 Sep 2008 10:50:26 +0200 [thread overview]
Message-ID: <20080917085026.GA27317@elte.hu> (raw)
In-Reply-To: <20080917170126.7d6a06d9.sfr@canb.auug.org.au>
* Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Avi,
>
> Today's linux-next build (x86_64 allmodconfig) failed like this:
>
> In file included from arch/x86/kvm/../../../virt/kvm/kvm_main.c:44:
> include/linux/intel-iommu.h:31:27: error: dma_remapping.h: No such file or directory
> drivers/pci/intr_remapping.c:8:25: error: intel-iommu.h: No such file or directory
>
> I needed to add the following patch to complete the merge of the kvm tree
> due to commit 14f776b8e0aa6724069a35bf4e172d93be74ba90 ("VT-d: Changes to
> support KVM") interacting with other changes ("x64,
> x2apic/intr-remap: ...") in the x86 tree.
hm, that looks like a non-trivial merge interaction. I'm wondering how
we should solve this. Avi, Jesse, any preferences?
Ingo
next prev parent reply other threads:[~2008-09-17 8:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 7:01 linux-next: kvm tree build failure Stephen Rothwell
2008-09-17 8:50 ` Ingo Molnar [this message]
2008-09-24 12:39 ` Avi Kivity
2008-09-24 16:18 ` Jesse Barnes
-- strict thread matches above, loose matches on Subject: below --
2008-10-15 5:47 Stephen Rothwell
2008-10-15 13:25 ` Avi Kivity
2008-12-18 11:05 Stephen Rothwell
2008-12-22 13:25 Stephen Rothwell
2008-12-29 5:17 ` Stephen Rothwell
2009-01-02 0:53 ` Stephen Rothwell
2009-01-04 11:08 ` Avi Kivity
2009-01-04 19:45 ` Hollis Blanchard
2009-01-04 19:55 ` Avi Kivity
2009-05-21 7:21 Stephen Rothwell
2009-05-21 7:32 ` Avi Kivity
2009-05-21 7:37 ` Boaz Harrosh
2009-05-21 7:39 ` Avi Kivity
2009-05-21 7:48 ` Boaz Harrosh
2009-05-21 10:05 ` Avi Kivity
2009-06-18 1:11 Stephen Rothwell
2009-06-18 4:25 ` Jaswinder Singh Rajput
2009-06-18 9:49 ` Avi Kivity
2009-06-23 5:53 Stephen Rothwell
2009-06-23 10:23 ` Avi Kivity
2009-08-13 2:58 Stephen Rothwell
2009-08-13 8:58 ` Avi Kivity
2010-01-11 8:07 Stephen Rothwell
2010-01-11 8:21 ` Stephen Rothwell
2010-01-11 10:27 ` Avi Kivity
2010-01-19 1:42 Stephen Rothwell
2010-01-19 7:57 ` Avi Kivity
2010-01-19 9:42 ` Stephen Rothwell
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=20080917085026.GA27317@elte.hu \
--to=mingo@elte.hu \
--cc=allen.m.kay@intel.com \
--cc=avi@qumranet.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=suresh.b.siddha@intel.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.