linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Rapoport <rppt@linux.vnet.ibm.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Vineet Gupta <vgupta@synopsys.com>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] arc/Kconfig: include mm/Kconfig inside "ARC system configuration"
Date: Fri, 29 Jun 2018 22:28:38 +0300	[thread overview]
Message-ID: <20180629192838.GE4799@rapoport-lnx> (raw)
In-Reply-To: <4c84ef6c-fa71-8b74-826a-d81dac8c71e7@infradead.org>

Hi Randy, 

On Fri, Jun 29, 2018 at 09:34:55AM -0700, Randy Dunlap wrote:
> On 06/29/2018 06:42 AM, Mike Rapoport wrote:
> > Otherwise mm configuration options show up in the top level menu.
> > 
> > Signed-off-by: Mike Rapoport <rppt@linux.vnet.ibm.com>
> 
> Hi Mike,
> 
> In which config tool does this matter?
> 
> For xconfig, it seems to me that this patch hides the MM menu, whereas
> before this patch, the MM menu is easy to find (although it could
> use some kind of heading).

With xconfig the menu gets into the top right pane when you click on "ARC
architecture configuration", similar to what one gets on x86 with
"Processor type and features" or "Kernel features" on ARM.

With menuconfig it looks a bit more prominent, note that mm options are
between "ARC Architecture Configuration" and "Networking support":

 .config - Linux/arc 4.18.0-rc2 Kernel Configuration
 ──────────────────────────────────────────────────────────────────────────────
  ┌─────────────── Linux/arc 4.18.0-rc2 Kernel Configuration ───────────────┐
  │  Arrow keys navigate the menu.  <Enter> selects submenus ---> (or empty │  
  │  submenus ----).  Highlighted letters are hotkeys.  Pressing <Y>        │  
  │  includes, <N> excludes, <M> modularizes features.  Press <Esc><Esc> to │  
  │  exit, <?> for Help, </> for Search.  Legend: [*] built-in  [ ]         │  
  │ ┌─────────────────────────────────────────────────────────────────────┐ │  
  │ │        *** Compiler: arc-elf-gcc (GCC) 7.3.0 ***                    │ │  
  │ │        General setup  --->                                          │ │  
  │ │    [*] Enable loadable module support  --->                         │ │  
  │ │    [*] Enable the block layer  --->                                 │ │  
  │ │        ARC Architecture Configuration  --->                         │ │  
  │ │    [ ] Allow for memory compaction                                  │ │  
  │ │    [*] Enable bounce buffers                                        │ │  
  │ │    [ ] Enable KSM for page merging                                  │ │  
  │ │    (4096) Low address space to protect from user allocation         │ │  
  │ │    [ ] Enable cleancache driver to cache clean pages if tmem is pres│ │  
  │ │    [ ] Contiguous Memory Allocator                                  │ │  
  │ │    < > Common API for compressed memory storage                     │ │  
  │ │    < > Low (Up to 2x) density storage for compressed pages          │ │  
  │ │    < > Memory allocator for compressed pages                        │ │  
  │ │    [ ] Enable idle page tracking                                    │ │  
  │ │    [ ] Collect percpu memory statistics                             │ │  
  │ │    [ ] Enable infrastructure for get_user_pages_fast() benchmarking │ │  
  │ │    (11) Maximum zone order                                          │ │  
  │ │    [*] Networking support  --->                                     │ │  
  │ │        Device Drivers  --->                                         │ │  
  │ │        Bus Support  --->                                            │ │  
  │ │        File systems  --->                                           │ │  
  │ │        Kernel hacking  --->                                         │ │  
  │ │        Security options  --->                                       │ │  
  │ │    -*- Cryptographic API  --->                                      │ │  
  │ │        Library routines  --->                                       │ │  
  │ │    [ ] Device power management core functionality                   │ │  
  │ │                                                                     │ │  
  │ └─────────────────────────────────────────────────────────────────────┘ │  
  ├─────────────────────────────────────────────────────────────────────────┤  
  │        <Select>    < Exit >    < Help >    < Save >    < Load >         │  
  └─────────────────────────────────────────────────────────────────────────┘  
    



> >  	default "12" if ARC_HUGEPAGE_16M
> >  	default "11"
> >  
> > +endmenu	 # "ARC Architecture Configuration"
> > +
> >  source "net/Kconfig"
> >  source "drivers/Kconfig"
> >  
> > 
> 
> 
> -- 
> ~Randy
> 

-- 
Sincerely yours,
Mike.


  reply	other threads:[~2018-06-29 19:33 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-29 13:42 [PATCH] arc/Kconfig: include mm/Kconfig inside "ARC system configuration" Mike Rapoport
2018-06-29 16:34 ` Randy Dunlap
2018-06-29 19:28   ` Mike Rapoport [this message]
2018-06-29 20:28     ` Randy Dunlap
2018-06-29 20:37       ` Vineet Gupta
2018-06-29 20:57       ` Mike Rapoport
2018-06-29 21:12         ` Vineet Gupta
2018-06-30  6:08           ` Randy Dunlap
2018-06-29 20:16 ` Vineet Gupta
2018-07-02 13:20 ` Christoph Hellwig
2018-07-02 14:29   ` Mike Rapoport

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=20180629192838.GE4799@rapoport-lnx \
    --to=rppt@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    --cc=vgupta@synopsys.com \
    /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;
as well as URLs for NNTP newsgroup(s).