From: Adrian Bunk <bunk@kernel.org>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
linux-kernel@vger.kernel.org
Subject: Re: x86 git acpi issue?
Date: Sat, 3 May 2008 10:13:32 +0300 [thread overview]
Message-ID: <20080503071332.GF5838@cs181133002.pp.htv.fi> (raw)
In-Reply-To: <481BACEC.8080902@zytor.com>
On Fri, May 02, 2008 at 05:08:12PM -0700, H. Peter Anvin wrote:
> Hiroshi Shimamoto wrote:
>> Hi,
>>
>> commit: afcab879e4044f952b7a031d5fd504e0feb7df41
>> visws: build fix
>>
>> breaks something around acpi on 32bit.
>> In my test box scsi driver complains and the kernel doesn't boot.
>>
>> I'm not sure, but when moving the acpi.o before legacy.o, it works.
>> --- a/arch/x86/pci/Makefile_32
>> +++ b/arch/x86/pci/Makefile_32
>> @@ -6,11 +6,11 @@ obj-$(CONFIG_PCI_DIRECT) += direct.o
>> obj-$(CONFIG_PCI_OLPC) += olpc.o
>> pci-y := fixup.o
>> +pci-$(CONFIG_ACPI) += acpi.o
>> pci-y += legacy.o irq.o
>> pci-$(CONFIG_X86_VISWS) := visws.o fixup.o
>> pci-$(CONFIG_X86_NUMAQ) := numa.o irq.o
>> -pci-$(CONFIG_ACPI) += acpi.o
>> pci-$(CONFIG_NUMA) += mp_bus_to_node.o
>> obj-y += $(pci-y) common.o early.o
>>
>> of cause this isn't correct patch, it's just a workaround for me.
>>
>
> The problem is that := should be += for the VISWS and NUMAQ lines. There
> is already a patch queued up to fix that.
Commit afcab879e4044f952b7a031d5fd504e0feb7df41 is the commit where Ingo
both _reverts_ his patch you describe in the x86 tree and additionally
moves pci-$(CONFIG_ACPI) in exactly the way that causes this breakage.
In the 4 hours between Ingo doing the += change and Ingo reverting his
own patch in the x86 tree it was in a pull request to Linus, so the
"queued up" patch is in Linus' tree but reverted in the x86 tree.
I saw neither the patch changing the :='s to += on linux-kernel nor does
"do not override the existing pci-y rule when adding visws or numaq
rules." in the commit description give any indication what the actual
problem was.
It's also not obvious why the revert with the subject "visws: build fix"
also moved the pci-$(CONFIG_ACPI) causing this bug here.
> -hpa
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next prev parent reply other threads:[~2008-05-03 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-03 0:06 Hiroshi Shimamoto
2008-05-03 0:08 ` H. Peter Anvin
2008-05-03 0:30 ` Hiroshi Shimamoto
2008-05-03 7:13 ` Adrian Bunk [this message]
2008-05-03 9:27 ` Thomas Gleixner
2008-05-03 9:45 ` Ingo Molnar
2008-05-03 10:02 ` Thomas Gleixner
2008-05-03 10:08 ` Sam Ravnborg
2008-05-03 11:10 ` Ingo Molnar
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=20080503071332.GF5838@cs181133002.pp.htv.fi \
--to=bunk@kernel.org \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®