From: Ingo Molnar <mingo@elte.hu>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Adrian Bunk <bunk@kernel.org>, "H. Peter Anvin" <hpa@zytor.com>,
Hiroshi Shimamoto <h-shimamoto@ct.jp.nec.com>,
linux-kernel@vger.kernel.org
Subject: Re: x86 git acpi issue?
Date: Sat, 3 May 2008 11:45:51 +0200 [thread overview]
Message-ID: <20080503094551.GA10805@elte.hu> (raw)
In-Reply-To: <alpine.LFD.1.10.0805031123420.6003@apollo.tec.linutronix.de>
* Thomas Gleixner <tglx@linutronix.de> wrote:
> On Sat, 3 May 2008, Adrian Bunk wrote:
> > 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.
>
> Right. This Makefile is a nasty trap. I looked into it and the fix for
> now is below. Long term this Makefile trickery needs to be cleaned up
> to avoid trapping into this again.
Thanks Thomas, i messed up that commit - i should have known that the
NUMAQ build fix looked _too_ easy ;-)
Ingo
next prev parent reply other threads:[~2008-05-03 9:46 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
2008-05-03 9:27 ` Thomas Gleixner
2008-05-03 9:45 ` Ingo Molnar [this message]
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=20080503094551.GA10805@elte.hu \
--to=mingo@elte.hu \
--cc=bunk@kernel.org \
--cc=h-shimamoto@ct.jp.nec.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--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
Powered by JetHome