From: Dave Hansen <dave@sr71.net>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, x86@kernel.org
Subject: Re: [PATCH 00/12] [v2] Reorganize x86 Kconfig menu
Date: Tue, 14 Jan 2014 14:12:25 -0800 [thread overview]
Message-ID: <52D5B649.9050103@sr71.net> (raw)
In-Reply-To: <20140114142533.GC29887@pd.tnic>
On 01/14/2014 06:25 AM, Borislav Petkov wrote:
> On Mon, Jan 13, 2014 at 11:22:45AM -0800, Dave Hansen wrote:
> * CONFIG_X86_X2APIC could go into "Processor Options and Features"
>
> * We should put "Processor family (...) --->" into the main menu since
> it is one of the most important ones.
>
> * "Preemption Model" could be merged with "x86 Scheduler Options"
>
> * Move CONFIG_SECCOMP, CONFIG_COMPAT_VDSO to obscure options?
I actually axed SECCOMP in another set of (arch-independent) patches.
> * Move CONFIG_PHYSICAL_START to "Memory and NUMA Options"
>
> * Maybe group CONFIG_RELOCATABLE, CONFIG_CC_STACKPROTECTOR,
> CONFIG_PHYSICAL_ALIGN to a separate "Kernel image options" menu.
This is used in concert with a few of the crash dump options, so I think
it makes sense to keep them grouped together.
> * CONFIG_CMDLINE_BOOL - I don't know about this one, it certainly
> doesn't fit anywhere..
>
> Anyway, just a couple of suggestions
Yup, thanks! Those are all good suggestions. I'll definitely take a
look at doing this in the next round. My focus at this point is to get
this set merged before I accrue too large of a pile.
prev parent reply other threads:[~2014-01-14 22:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-13 19:22 [PATCH 00/12] [v2] Reorganize x86 Kconfig menu Dave Hansen
2014-01-13 19:22 ` [PATCH 01/12] x86 Kconfig: create extended platforms menu Dave Hansen
2014-01-13 19:22 ` [PATCH 02/12] x86 Kconfig: memory options Dave Hansen
2014-01-13 19:22 ` [PATCH 03/12] x86 Kconfig: move highmem Dave Hansen
2014-01-13 19:22 ` [PATCH 04/12] x86 Kconfig: processor options menu Dave Hansen
2014-01-13 19:22 ` [PATCH 05/12] x86 Kconfig: processor drivers Dave Hansen
2014-01-13 19:22 ` [PATCH 06/12] x86 Kconfig: scheduler options Dave Hansen
2014-01-13 19:22 ` [PATCH 07/12] x86 Kconfig: move memtest Dave Hansen
2014-01-13 19:22 ` [PATCH 08/12] x86 Kconfig: bury obscure options Dave Hansen
2014-01-13 19:22 ` [PATCH 09/12] x86 Kconfig: create mtrr menu under processsor options Dave Hansen
2014-01-13 19:22 ` [PATCH 10/12] x86 Kconfig: MCE menu Dave Hansen
2014-01-13 19:22 ` [PATCH 11/12] x86 Kconfig: create x86/Kconfig.virt Dave Hansen
2014-01-13 22:46 ` Paolo Bonzini
2014-01-13 23:00 ` Dave Hansen
2014-01-13 23:12 ` Paolo Bonzini
2014-01-14 0:04 ` Dave Hansen
2014-01-13 19:23 ` [PATCH 12/12] x86 Kconfig: move paravirt under "Virtualization" Dave Hansen
2014-01-14 14:25 ` [PATCH 00/12] [v2] Reorganize x86 Kconfig menu Borislav Petkov
2014-01-14 22:12 ` Dave Hansen [this message]
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=52D5B649.9050103@sr71.net \
--to=dave@sr71.net \
--cc=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=x86@kernel.org \
/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