From: Robert Richter <robert.richter@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Thomas Gleixner <tglx@linutronix.de>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] x86/pci: patches for tip/x86/unify-pci
Date: Fri, 11 Jul 2008 10:20:43 +0200 [thread overview]
Message-ID: <20080711082042.GT7963@erda.amd.com> (raw)
In-Reply-To: <20080710195425.GB23322@elte.hu>
On 10.07.08 21:54:25, Ingo Molnar wrote:
>
> * Sam Ravnborg <sam@ravnborg.org> wrote:
>
> > On Thu, Jul 10, 2008 at 08:12:34PM +0200, Ingo Molnar wrote:
> > >
> > > * Ingo Molnar <mingo@elte.hu> wrote:
> > >
> > > > * Robert Richter <robert.richter@amd.com> wrote:
> > > >
> > > > > This patch series contains patches for tip/x86/unify-pci. It fixes
> > > > > NUMA initialization code reflecting latest changes in tip/master.
> > > > > Also there are build fixes and minor cleanups. Patch #5 is a cherry
> > > > > pick that fixes build on UP systems. Code reboots for smp/nosmp,
> > > > > acpi/noacpi, numaq, 32/64bit. It compiles for visws.
> > > >
> > > > thanks Robert. Today i've eliminated the VISWS subarch which greatly
> > > > simplified your series. I've picked up these two fixes:
> > > >
> > > > Robert Richter (2):
> > > > x86/pci merge: fixing numaq initialization
> > > > x86/pci: fix warnings in subsys_initcall functions
> > >
> > > btw., this is how arch/x86/pci/Makefile looks like now in tip/master:
> > >
> > > ----------------------------------------->
> > > pci-y := fixup.o
> > > pci-$(CONFIG_ACPI) += acpi.o
> > > pci-y += legacy.o irq.o
> > >
> > > pci-$(CONFIG_X86_VISWS) += visws.o
> > >
> > > pci-$(CONFIG_X86_NUMAQ) += numa.o
> > >
> > > obj-y += $(pci-y) common.o early.o
> > > obj-y += amd_bus.o
> > > <-----------------------------------------
> >
> > So if I am not mistaken you can kill pci-y entirely:
Yes, but...
> >
> > obj-y := fixup.o
... this is with a plus:
obj-y += fixup.o
> > obj-$(CONFIG_ACPI) += acpi.o
> > obj-y += legacy.o irq.o
> >
> > obj-$(CONFIG_X86_VISWS) += visws.o
> >
> > obj-$(CONFIG_X86_NUMAQ) += numa.o
> >
> > obj-y += common.o early.o
> > obj-y += amd_bus.o
>
> ah, indeed :-) Very nice.
>
> Ingo
>
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next prev parent reply other threads:[~2008-07-11 8:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-10 16:58 [PATCH 0/5] x86/pci: patches for tip/x86/unify-pci Robert Richter
2008-07-10 16:58 ` [PATCH 1/5] x86/pci: Fix build error for X86_VISWS Robert Richter
2008-07-10 16:58 ` [PATCH 2/5] x86/pci: Makefile merge: Changing 32bit ordering Robert Richter
2008-07-10 16:58 ` [PATCH 3/5] x86/pci merge: Fixing numaq initialization Robert Richter
2008-07-10 17:51 ` Yinghai Lu
2008-07-10 16:58 ` [PATCH 4/5] x86/pci: Fix warnings in subsys_initcall functions Robert Richter
2008-07-10 16:58 ` [PATCH 5/5] x86: build fix for "x86: fix C1E && nx6325 stability problem" Robert Richter
2008-07-10 17:17 ` [PATCH 0/5] x86/pci: patches for tip/x86/unify-pci Ingo Molnar
2008-07-10 18:12 ` Ingo Molnar
2008-07-10 19:52 ` Sam Ravnborg
2008-07-10 19:54 ` Ingo Molnar
2008-07-11 8:20 ` Robert Richter [this message]
2008-07-11 10:22 ` Sam Ravnborg
2008-07-11 10:23 ` Ingo Molnar
2008-07-11 10:28 ` Sam Ravnborg
2008-07-11 8:43 ` Robert Richter
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=20080711082042.GT7963@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.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