From: Ravikiran Thirumalai <kiran@scalemp.com>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: linux-kernel@vger.kernel.org, mm-commits@vger.kernel.org,
gcosta@redhat.com, mingo@elte.hu, tglx@linutronix.de
Subject: Re: + x86-vsmp-build-fixes.patch added to -mm tree
Date: Tue, 18 Mar 2008 00:28:02 -0700 [thread overview]
Message-ID: <20080318072802.GH6091@localdomain> (raw)
In-Reply-To: <86802c440803172226yb867326rb595b36b03e6c4b9@mail.gmail.com>
On Mon, Mar 17, 2008 at 10:26:55PM -0700, Yinghai Lu wrote:
>On Mon, Mar 17, 2008 at 10:14 PM, <akpm@linux-foundation.org> wrote:
>> ...
>> Subject: x86: vsmp build fixes
>> From: Glauber Costa <gcosta@redhat.com>
>>
>> VSMP depends on PCI, but the file is now compiled conditionally on PARAVIRT,
>> no VSMP, so enclose everything in an ifdef CONFIG_PCI.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
...
>
>in arch/x86/Kconfig
>
>config PCI
> bool "PCI support" if !X86_VISWS && !X86_VSMP
> depends on !X86_VOYAGER
> default y
> select ARCH_SUPPORTS_MSI if (X86_LOCAL_APIC && X86_IO_APIC)
> help
> Find out whether you have a PCI motherboard. PCI is the name of a
> bus system, i.e. the way the CPU talks to the other stuff inside
> your box. Other bus systems are ISA, EISA, MicroChannel (MCA) or
> VESA. If you have PCI, say Y, otherwise N.
>
>will make sure if X86_VSMP, the PCI=y
>
>so NAK this patch.
>
Not really, as you can tell from the description Glauber provided above.
Btw, I had something similar to this cooking for the build breakage, along
with a few more updates (is_vsmp_box() is broken on vsmp). Thanks Glauber
for this patch.
Thanks,
Kiran
next prev parent reply other threads:[~2008-03-18 7:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200803180514.m2I5ElVJ015693@imap1.linux-foundation.org>
2008-03-18 5:26 ` + x86-vsmp-build-fixes.patch added to -mm tree Yinghai Lu
2008-03-18 7:28 ` Ravikiran Thirumalai [this message]
2008-03-18 7:56 ` Yinghai Lu
2008-03-18 8:25 ` Yinghai Lu
2008-03-18 8:37 ` Fwd: " Yinghai Lu
2008-03-18 9:40 ` Glauber Costa
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=20080318072802.GH6091@localdomain \
--to=kiran@scalemp.com \
--cc=gcosta@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=mm-commits@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yhlu.kernel@gmail.com \
/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