linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Christoph Hellwig <hch@infradead.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux MM <linux-mm@kvack.org>, X86 ML <x86@kernel.org>
Subject: Re: [PATCH] x86: make Memory Management options more visible
Date: Mon, 2 Jul 2018 08:48:10 -0700	[thread overview]
Message-ID: <afcb4a42-891a-d732-f072-79c0a1fc49f0@infradead.org> (raw)
In-Reply-To: <20180702140612.GA7333@infradead.org>

On 07/02/2018 07:06 AM, Christoph Hellwig wrote:
> On Sun, Jul 01, 2018 at 07:48:38PM -0700, Randy Dunlap wrote:
>> From: Randy Dunlap <rdunlap@infradead.org>
>>
>> Currently for x86, the "Memory Management" kconfig options are
>> displayed under "Processor type and features."  This tends to
>> make them hidden or difficult to find.
>>
>> This patch makes Memory Managment options a first-class menu by moving
>> it away from "Processor type and features" and into the main menu.
>>
>> Also clarify "endmenu" lines with '#' comments of their respective
>> menu names, just to help people who are reading or editing the
>> Kconfig file.
>>
>> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
> 
> Hmm, can you take off from this for now and/or rebase it on top of
> this series:
> 
> 	http://git.infradead.org/users/hch/misc.git/shortlog/refs/heads/kconfig-cleanups
> 

Sure, no problem.

-- 
~Randy

  reply	other threads:[~2018-07-02 15:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-02  2:48 Randy Dunlap
2018-07-02 14:06 ` Christoph Hellwig
2018-07-02 15:48   ` Randy Dunlap [this message]
2018-07-03  8:28     ` 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=afcb4a42-891a-d732-f072-79c0a1fc49f0@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.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