public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Fenghua Yu <fenghua.yu@intel•com>
Cc: Alexander Beregalov <a.beregalov@gmail•com>,
	LKML <linux-kernel@vger•kernel.org>,
	"Luck, Tony" <tony.luck@intel•com>,
	"Woodhouse, David" <david.woodhouse@intel•com>,
	linux-next@vger•kernel.org, mingo@elte•hu,
	fujita.tomonori@lab•ntt.co.jp, adobriyan@gmail•com
Subject: Re: build failure at x86/kernel/pci-dma.c with !CONFIG_PCI
Date: Fri, 24 Oct 2008 16:56:24 +1100	[thread overview]
Message-ID: <20081024165624.7d9bfae3.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20081023235100.GA2192@linux-os.sc.intel.com>

[-- Attachment #1: Type: text/plain, Size: 830 bytes --]

On Thu, 23 Oct 2008 16:51:00 -0700 Fenghua Yu <fenghua.yu@intel•com> wrote:
>
> On Thu, Oct 23, 2008 at 04:09:52PM -0700, Alexander Beregalov wrote:
> > arch/x86/kernel/built-in.o: In function `iommu_setup':
> > pci-dma.c:(.init.text+0x36ad): undefined reference to `forbid_dac'
> > pci-dma.c:(.init.text+0x36cc): undefined reference to `forbid_dac'
> > pci-dma.c:(.init.text+0x3711): undefined reference to `forbid_dac
> > 
> > commit 5b6985ce8ec7127b4d60ad450b64ca8b82748a3b
> > Author: Fenghua Yu <fenghua.yu@intel•com>
> > Date:   Thu Oct 16 18:02:32 2008 -0700
> > 
> >     intel-iommu: IA64 support
> 
> Could you please try the following fix patch?

I have added this patch to today's linux-next.

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  parent reply	other threads:[~2008-10-24  5:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <a4423d670810231609h76323d2fqa4ed7d9ba0a46e3b@mail.gmail.com>
2008-10-23 23:51 ` build failure at x86/kernel/pci-dma.c with !CONFIG_PCI Fenghua Yu
2008-10-23 23:57   ` FUJITA Tomonori
2008-10-23 23:58   ` Alexander Beregalov
2008-10-24  5:56   ` Stephen Rothwell [this message]
2008-10-24 18:10   ` Jesse Barnes

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=20081024165624.7d9bfae3.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=a.beregalov@gmail$(echo .)com \
    --cc=adobriyan@gmail$(echo .)com \
    --cc=david.woodhouse@intel$(echo .)com \
    --cc=fenghua.yu@intel$(echo .)com \
    --cc=fujita.tomonori@lab$(echo .)ntt.co.jp \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=mingo@elte$(echo .)hu \
    --cc=tony.luck@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