From: Jeff Garzik <jgarzik@pobox.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: ak@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH][2.4.26-pre5][x86_64] pci=noapci bogus warning
Date: Sat, 20 Mar 2004 19:55:39 -0500 [thread overview]
Message-ID: <405CE80B.9060503@pobox.com> (raw)
In-Reply-To: <200403202310.i2KNA3sp006345@harpo.it.uu.se>
Mikael Pettersson wrote:
> diff -ruN linux-2.4.26-pre5/arch/x86_64/kernel/pci-pc.c linux-2.4.26-pre5.x86_64-pci=noacpi-fix/arch/x86_64/kernel/pci-pc.c
> --- linux-2.4.26-pre5/arch/x86_64/kernel/pci-pc.c 2003-11-29 00:28:11.000000000 +0100
> +++ linux-2.4.26-pre5.x86_64-pci=noacpi-fix/arch/x86_64/kernel/pci-pc.c 2004-03-20 23:22:27.000000000 +0100
> @@ -645,6 +645,9 @@
> } else if (!strncmp(str, "lastbus=", 8)) {
> pcibios_last_bus = simple_strtol(str+8, NULL, 0);
> return NULL;
> + } else if (!strncmp(str, "noacpi", 6)) {
> + acpi_noirq_set();
> + return NULL;
> }
Seem to me this runs afoul of the frequent "acpi"/"apic" typo...
Jeff
next prev parent reply other threads:[~2004-03-21 0:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-20 23:10 [PATCH][2.4.26-pre5][x86_64] pci=noapci bogus warning Mikael Pettersson
2004-03-21 0:55 ` Jeff Garzik [this message]
2004-03-22 0:38 ` Andi Kleen
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=405CE80B.9060503@pobox.com \
--to=jgarzik@pobox.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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