linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Rientjes <rientjes@google.com>
To: Randy Dunlap <rdunlap@xenotime.net>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Thomas Gleixner <tglx@linutronix.de>
Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	x86@kernel.org
Subject: Re: [PATCH] config menu: move ZONE_DMA under a menu
Date: Mon, 16 Jan 2012 15:50:28 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.00.1201161548580.16270@chino.kir.corp.google.com> (raw)
In-Reply-To: <4F14811E.6090107@xenotime.net>

On Mon, 16 Jan 2012, Randy Dunlap wrote:

> From: Randy Dunlap <rdunlap@xenotime.net>
> 
> Move the ZONE_DMA kconfig symbol under a menu item instead
> of having it listed before everything else in
> "make {xconfig | gconfig | nconfig | menuconfig}".
> 
> This drops the first line of the top-level kernel config menu
> (in 3.2) below and moves it under "Processor type and features".
> 
>           [*] DMA memory allocation support
>               General setup  --->
>           [*] Enable loadable module support  --->
>           [*] Enable the block layer  --->
>               Processor type and features  --->
>               Power management and ACPI options  --->
>               Bus options (PCI etc.)  --->
>               Executable file formats / Emulations  --->
> 
> 
> Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
> Cc: David Rientjes <rientjes@google.com>

Acked-by: David Rientjes <rientjes@google.com>

Thanks!

  reply	other threads:[~2012-01-16 23:50 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-16 19:57 [PATCH] config menu: move ZONE_DMA under a menu Randy Dunlap
2012-01-16 23:50 ` David Rientjes [this message]
2012-01-17 17:24 ` [tip:x86/urgent] x86/kconfig: Move the ZONE_DMA entry " tip-bot for Randy Dunlap

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=alpine.DEB.2.00.1201161548580.16270@chino.kir.corp.google.com \
    --to=rientjes@google.com \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=mingo@elte.hu \
    --cc=rdunlap@xenotime.net \
    --cc=tglx@linutronix.de \
    --cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).