LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Luis R. Rodriguez" <mcgrof@do-not-panic.com>
To: bhelgaas@google.com, mingo@redhat.com, tglx@linutronix.de,
hpa@zytor.com, pure.logic@nexus-software.ie, jgross@suse.com,
luto@amacapital.net, andy.shevchenko@gmail.com,
thomas.petazzoni@free-electrons.com, JBeulich@suse.com,
bp@suse.de
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org,
x86@kernel.org, "Luis R. Rodriguez" <mcgrof@suse.com>
Subject: [RFC v1 0/2] x86: kconfig: simplify APIC entries
Date: Tue, 10 Mar 2015 16:14:33 -0700 [thread overview]
Message-ID: <1426029275-9594-1-git-send-email-mcgrof@do-not-panic.com> (raw)
From: "Luis R. Rodriguez" <mcgrof@suse.com>
There's quite a bit of Kconfig entries related to X86_LOCAL_APIC
and X86_IO_APIC, and all for 32-bit purposes. Since 32-bit isn't in
a magical state of flux we now *should* know when to enable or disable
APIC stuff for these systems. Through history we've observed for
instance PCI_MSI requires these under specific scenarios, just enable
it for those learned scenarios and expect future requirements to also
be explicit about the requirements on 32-bit. This lets us remove
clutter (3 Kconfig entries) from x86 Kconfig simply for 32-bit build
purposes.
Luis R. Rodriguez (2):
x86: kconfig: simplify enabling [IO]APIC for PCI_MSI
x86: kconfig: remove UP [IO]APIC options
Documentation/PCI/MSI-HOWTO.txt | 5 +----
arch/x86/Kconfig | 33 ++-------------------------------
drivers/pci/Kconfig | 2 ++
3 files changed, 5 insertions(+), 35 deletions(-)
--
2.3.2.209.gd67f9d5.dirty
next reply other threads:[~2015-03-10 23:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 23:14 Luis R. Rodriguez [this message]
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
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:
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=1426029275-9594-1-git-send-email-mcgrof@do-not-panic.com \
--to=mcgrof@do-not-panic.com \
--cc=JBeulich@suse.com \
--cc=andy.shevchenko@gmail.com \
--cc=bhelgaas@google.com \
--cc=bp@suse.de \
--cc=hpa@zytor.com \
--cc=jgross@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=mcgrof@suse.com \
--cc=mingo@redhat.com \
--cc=pure.logic@nexus-software.ie \
--cc=tglx@linutronix.de \
--cc=thomas.petazzoni@free-electrons.com \
--cc=x86@kernel.org \
--subject='Re: [RFC v1 0/2] x86: kconfig: simplify APIC entries' \
/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
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).