From: ebiederm@xmission.com (Eric W. Biederman)
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org, Jesper Juhl <jesper.juhl@gmail.com>,
gregkh@suse.de, linux-pci@atrey.karlin.mff.cuni.cz
Subject: Re: [2.6 patch] HT_IRQ must depend on PCI
Date: Sun, 08 Oct 2006 07:00:31 -0600 [thread overview]
Message-ID: <m1odsnufm8.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20061008040638.GF29474@stusta.de> (Adrian Bunk's message of "Sun, 8 Oct 2006 06:06:38 +0200")
Adrian Bunk <bunk@stusta.de> writes:
Looks good to me.
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
> CONFIG_PCI=n, CONFIG_HT_IRQ=y results in the following compile error:
>
> <-- snip -->
>
> ...
> LD vmlinux
> arch/i386/mach-generic/built-in.o: In function `apicid_to_node':
> summit.c:(.text+0x53): undefined reference to `apicid_2_node'
> arch/i386/kernel/built-in.o: In function `arch_setup_ht_irq':
> (.text+0xcf79): undefined reference to `write_ht_irq_low'
> arch/i386/kernel/built-in.o: In function `arch_setup_ht_irq':
> (.text+0xcf85): undefined reference to `write_ht_irq_high'
> arch/i386/kernel/built-in.o: In function `k7nops':
> alternative.c:(.data+0x1358): undefined reference to `mask_ht_irq'
> alternative.c:(.data+0x1360): undefined reference to `unmask_ht_irq'
> make[1]: *** [vmlinux] Error 1
>
> <-- snip -->
>
> Bug report by Jesper Juhl.
>
> Signed-off-by: Adrian Bunk <bunk@stusta.de>
>
> --- linux-2.6/drivers/pci/Kconfig.old 2006-10-08 05:55:51.000000000 +0200
> +++ linux-2.6/drivers/pci/Kconfig 2006-10-08 05:56:14.000000000 +0200
> @@ -55,7 +55,7 @@
> config HT_IRQ
> bool "Interrupts on hypertransport devices"
> default y
> - depends on X86_LOCAL_APIC && X86_IO_APIC
> + depends on PCI && X86_LOCAL_APIC && X86_IO_APIC
> help
> This allows native hypertransport devices to use interrupts.
>
prev parent reply other threads:[~2006-10-08 13:02 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-08 4:06 Adrian Bunk
2006-10-08 13:00 ` Eric W. Biederman [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=m1odsnufm8.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=bunk@stusta.de \
--cc=gregkh@suse.de \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@atrey.karlin.mff.cuni.cz \
/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
Powered by JetHome