From: "Bryan O'Donoghue" <pure.logic@nexus-software.ie>
To: Jan Beulich <JBeulich@suse.com>,
mingo@elte.hu, tglx@linutronix.de, hpa@zytor.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/Kconfig: simplify X86_UP_APIC handling
Date: Fri, 06 Feb 2015 00:00:25 +0000 [thread overview]
Message-ID: <54D40419.3050701@nexus-software.ie> (raw)
In-Reply-To: <54D39AFC020000780005D684@mail.emea.novell.com>
On 05/02/15 15:31, Jan Beulich wrote:
> We don't really need a helper symbol for that. For one, it's
> pointlessly getting set to Y for all configurations (even 64-bit ones).
> And then the purpose can be fulfilled by suitably adjusting
> X86_UP_APIC: Hide its prompt when PCI_MSI, and default it to PCI_MSI.
ACK
tested works for me the same as the previous patch - plus it's one
symbol les.
Tested-by: Bryan O'Donoghue <pure.logic@nexus-software.ie>
next prev parent reply other threads:[~2015-02-06 0:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 15:31 [PATCH] x86/Kconfig: simplify X86_UP_APIC handling Jan Beulich
2015-02-06 0:00 ` Bryan O'Donoghue [this message]
2015-02-19 0:27 ` [tip:x86/build] x86/Kconfig: Simplify " tip-bot for Jan Beulich
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=54D40419.3050701@nexus-software.ie \
--to=pure.logic@nexus-software.ie \
--cc=JBeulich@suse.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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