From: Andrew Morton <akpm@osdl.org>
To: Michael Bakos <bakhos@msi.umn.edu>
Cc: linux-kernel@vger.kernel.org, Andrew de Quincey <adq_dvb@lidskialf.net>
Subject: Re: compile error for Opteron CPU with kernel 2.6.0-test2
Date: Thu, 31 Jul 2003 21:21:05 -0700 [thread overview]
Message-ID: <20030731212105.75fb4191.akpm@osdl.org> (raw)
In-Reply-To: <Pine.SGI.4.33.0307312127190.23643-100000@ir12.msi.umn.edu>
Michael Bakos <bakhos@msi.umn.edu> wrote:
>
> that patch did fix the cpumask_t problem, however another one is present
>
> CC arch/x86_64/kernel/mpparse.o
> arch/x86_64/kernel/mpparse.c: In function `mp_parse_prt':
> arch/x86_64/kernel/mpparse.c:899: error: too few arguments to function
> `acpi_pci_link_get_irq'
> make[1]: *** [arch/x86_64/kernel/mpparse.o] Error 1
> make: *** [arch/x86_64/kernel] Error 2
OK, I'd be doing this:
arch/x86_64/kernel/mpparse.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletion(-)
diff -puN arch/x86_64/kernel/mpparse.c~nforce2-acpi-fixes-fix arch/x86_64/kernel/mpparse.c
--- 25/arch/x86_64/kernel/mpparse.c~nforce2-acpi-fixes-fix 2003-07-31 21:18:45.000000000 -0700
+++ 25-akpm/arch/x86_64/kernel/mpparse.c 2003-07-31 21:18:59.000000000 -0700
@@ -896,7 +896,8 @@ void __init mp_parse_prt (void)
/* Need to get irq for dynamic entry */
if (entry->link.handle) {
- irq = acpi_pci_link_get_irq(entry->link.handle, entry->link.index);
+ irq = acpi_pci_link_get_irq(entry->link.handle,
+ entry->link.index, NULL, NULL);
if (!irq)
continue;
}
_
next prev parent reply other threads:[~2003-08-01 4:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 15:59 compile error for Opteron CPU with kernel 2.6.0-test2 Michael Bakos
2003-07-31 21:59 ` Andrew Morton
2003-08-01 1:08 ` Michael Bakos
2003-08-01 1:11 ` Michael Bakos
2003-08-01 1:27 ` Andrew Morton
2003-08-01 2:39 ` Michael Bakos
2003-08-01 4:21 ` Andrew Morton [this message]
2003-08-01 14:36 ` Andrew de Quincey
2003-08-01 3:12 ` Michael Bakos
2003-08-01 18:01 ` Bryan O'Sullivan
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=20030731212105.75fb4191.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=adq_dvb@lidskialf.net \
--cc=bakhos@msi.umn.edu \
--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