From: Ingo Molnar <mingo@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] x86: Cleanup Kconfig
Date: Tue, 2 Jun 2015 13:35:42 +0200 [thread overview]
Message-ID: <20150602113542.GA3443@gmail.com> (raw)
In-Reply-To: <20150602091455.GW19282@twins.programming.kicks-ass.net>
* Peter Zijlstra <peterz@infradead.org> wrote:
>
> While looking at arch/x86/Kconfig I noticed a lot of if X86_{32,64}
> clauses in the X86 symbol. Its much simpler to simply but these selects
> in the right symbol and do away with the conditionals.
>
> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> ---
> arch/x86/Kconfig | 30 +++++++++++++++---------------
> 1 file changed, 15 insertions(+), 15 deletions(-)
>
> diff --git a/arch/x86/Kconfig b/arch/x86/Kconfig
> index 8fec04407245..a259db4cfe8c 100644
> --- a/arch/x86/Kconfig
> +++ b/arch/x86/Kconfig
> @@ -11,6 +11,12 @@ config X86_32
> depends on !64BIT
> select CLKSRC_I8253
> select HAVE_UID16
> + select HAVE_AOUT
> + select HAVE_GENERIC_DMA_COHERENT
> + select ARCH_WANT_IPC_PARSE_VERSION
> + select MODULES_USE_ELF_REL
> + select CLONE_BACKWARDS
> + select OLD_SIGACTION
So I'd rather do it the other way around: move the remaining selects from X86_32
and X86_64 to the X86 section, and maybe group them by bitness.
The advantage: accidental duplication is more obviously wrong and a single
feature's bitness-presence is obvious at a glance.
Thanks,
Ingo
next prev parent reply other threads:[~2015-06-02 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-02 9:14 [RFC][PATCH] x86: Cleanup Kconfig Peter Zijlstra
2015-06-02 11:35 ` Ingo Molnar [this message]
2015-06-02 15:30 ` Peter Zijlstra
2015-06-03 7:26 ` Ingo Molnar
2015-06-03 7:41 ` Ingo Molnar
2015-06-03 13:59 ` Dave Jones
2015-06-03 16:19 ` Ingo Molnar
2015-06-03 17:11 ` Dave Jones
2015-06-03 9:30 ` [tip:x86/core] x86/kconfig: Reorganize arch feature Kconfig select's tip-bot for Ingo Molnar
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=20150602113542.GA3443@gmail.com \
--to=mingo@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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