public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: "Randy.Dunlap" <rddunlap@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>, ak@suse.de
Subject: Re: [PATCH] PCI/x86-64: build with PCI=n
Date: Thu, 9 Dec 2004 12:42:23 -0800	[thread overview]
Message-ID: <20041209204223.GA27309@kroah.com> (raw)
In-Reply-To: <20041130172354.2bd60e89.rddunlap@osdl.org>

On Tue, Nov 30, 2004 at 05:23:54PM -0800, Randy.Dunlap wrote:
> 
> Fix (most of) x64-64 kernel build for CONFIG_PCI=n.  Fixes these 2 errors:
> 
> 1. arch/x86_64/kernel/built-in.o(.text+0x8186): In function `quirk_intel_irqbalance':
> : undefined reference to `raw_pci_ops'
> 
> Kconfig change:
> 2. arch/x86_64/kernel/pci-gart.c:194: error: `pci_bus_type' undeclared (first use in this function)
> 
> Still does not fix this one:
> drivers/built-in.o(.text+0x3dcd8): In function `pnpacpi_allocated_resource':
> : undefined reference to `pcibios_penalize_isa_irq'
> 
> Signed-off-by: Randy Dunlap <rddunlap@osdl.org>

Applied, thanks.

greg k-h

      reply	other threads:[~2004-12-09 20:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-01  1:23 [PATCH] PCI/x86-64: build with PCI=n Randy.Dunlap
2004-12-09 20:42 ` Greg KH [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=20041209204223.GA27309@kroah.com \
    --to=greg@kroah.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rddunlap@osdl.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