LKML Archive on
help / color / mirror / Atom feed
From: David Rientjes <>
To: "Luis R. Rodriguez" <>
	"Luis R. Rodriguez" <>,
	Ingo Molnar <>
Subject: Re: [RFC v1 2/2] x86: kconfig: remove UP [IO]APIC options
Date: Tue, 10 Mar 2015 17:58:27 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Tue, 10 Mar 2015, Luis R. Rodriguez wrote:

> From: "Luis R. Rodriguez" <>
> These were here mostly to help as wrappers for PCI_MSI
> under certain UP 32-bit build scenarios, now that PCI_MSI
> properly selects what it needs and when it needs it these
> Kconfig options are now only enabling users reduce the size
> of 32-bit kernels optionally. Since 32-bit kernels are not
> in a huge state of flux and since there is no penalty for
> adding APIC support other than a bit of size moving forward
> we simply expect folks to enable APIC options on 32-bit systems
> when a system needs it, as with PCI_MSI. This lets us remove
> clutter from the x86 Kconfig file.

Check out Linus's latest tree at 
git:// and see 
how it looks after commit 50849eefea3b ("x86/Kconfig: Simplify X86_UP_APIC 
handling") and commit b1da1e715d4f ("x86/Kconfig: Simplify X86_IO_APIC 

  reply	other threads:[~2015-03-11  0:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-10 23:14 [RFC v1 0/2] x86: kconfig: simplify APIC entries Luis R. Rodriguez
2015-03-10 23:14 ` [RFC v1 1/2] x86: kconfig: simplify enabling [IO]APIC for PCI_MSI Luis R. Rodriguez
2015-03-11  0:49   ` David Rientjes
2015-03-11 23:03     ` Luis R. Rodriguez
2015-03-10 23:14 ` [RFC v1 2/2] x86: kconfig: remove UP [IO]APIC options Luis R. Rodriguez
2015-03-11  0:58   ` David Rientjes [this message]
2015-03-11 18:35     ` Luis R. Rodriguez

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).