From: Greg KH <greg@kroah.com>
To: "Martin J. Bligh" <Martin.Bligh@us.ibm.com>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.8-pre3 full compile - warnings
Date: Sun, 14 Apr 2002 11:04:33 -0700 [thread overview]
Message-ID: <20020414180433.GB18238@kroah.com> (raw)
In-Reply-To: <1605.1018774441@ocs3.intra.ocs.com.au> <2425212891.1018783655@[10.10.2.3]>
On Sun, Apr 14, 2002 at 11:27:36AM -0700, Martin J. Bligh wrote:
> > Although everything compiled, it did not link because of missing symbols.
> >
> > arch/i386/kernel/pci-pc.o: In function `pci_conf1_read':
> > arch/i386/kernel/pci-pc.o(.text+0xa3): undefined reference to
> > `mp_bus_id_to_local' arch/i386/kernel/pci-pc.o: In function
> > `pci_conf1_write':
> > arch/i386/kernel/pci-pc.o(.text+0x2c3): undefined reference to
> > `mp_bus_id_to_local' arch/i386/kernel/pci-pc.o: In function
> > `pci_fixup_i450nx':
> > arch/i386/kernel/pci-pc.o(.text+0x1c01): undefined reference to
> > `quad_local_to_mp_bus_id' arch/i386/kernel/pci-pc.o(.text+0x1c28):
> > undefined reference to `quad_local_to_mp_bus_id'
> > arch/i386/kernel/pci-pc.o: In function `pcibios_init':
> > arch/i386/kernel/pci-pc.o(.text.init+0xbd): undefined reference to
> > `quad_local_to_mp_bus_id' drivers/video/neofb.o: In function
> > `neofb_setup':
>
> Looks like someone screwed up arch/i386/kernel/mpparse.c
> between pre2 and pre3 - at a glance, it looked like someone
> took an old version of the file without my changes to support
> multi-quad PCI on NUMA-Q, and hacked it forward without changing
> it properly ...
In looking at the changesets, it seems that the offending party is the
ACPI group. I'd go complain to them :)
greg k-h
next prev parent reply other threads:[~2002-04-14 19:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-14 8:54 2.5.8-pre3 full compile - warnings Keith Owens
2002-04-14 18:27 ` Martin J. Bligh
2002-04-14 18:04 ` Greg KH [this message]
2002-04-15 17:32 ` Greg KH
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=20020414180433.GB18238@kroah.com \
--to=greg@kroah.com \
--cc=Martin.Bligh@us.ibm.com \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.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