From: Sachin Sant <sachinp@in.ibm.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
dwmw2@infradead.org
Subject: Next April 30: x86 allnoconfig failure (iommu)
Date: Thu, 30 Apr 2009 14:53:11 +0530 [thread overview]
Message-ID: <49F96DFF.2060105@in.ibm.com> (raw)
In-Reply-To: <20090430172923.bf9697c2.sfr@canb.auug.org.au>
Todays Next tree build(x86 allnoconfig) failed with following
error.
arch/x86/built-in.o: In function `iommu_setup':
pci-dma.c:(.init.text+0x3101): undefined reference to `iommu_pass_through'
arch/x86/built-in.o: In function `pci_swiotlb_init':
(.init.text+0x805a): undefined reference to `iommu_pass_through'
make: *** [.tmp_vmlinux1] Error 1
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
prev parent reply other threads:[~2009-04-30 9:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 7:29 linux-next: Tree for April 30 Stephen Rothwell
2009-04-30 9:23 ` Sachin Sant [this message]
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=49F96DFF.2060105@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=mingo@elte.hu \
--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;
as well as URLs for NNTP newsgroup(s).