linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Josh Triplett <josh@joshtriplett.org>
To: linux-kernel@vger.kernel.org
Cc: Thomas Gleixner <tglx@linutronix.de>,
	Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
	x86@kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
	Suresh Siddha <suresh.b.siddha@intel.com>
Subject: [PATCH 4/5] x86, defconfig: Turn off CONFIG_BLK_DEV_RAM
Date: Sun, 2 Sep 2012 22:21:21 -0700	[thread overview]
Message-ID: <2521e983a63595cd7a331236d929577660f89c72.1346649518.git.josh@joshtriplett.org> (raw)
In-Reply-To: <cover.1346649518.git.josh@joshtriplett.org>

The vast majority of systems either use initramfs or mount a root
filesystem directly from the kernel.  Distros have defaulted to
initramfs for years.  Only highly specialized systems would use an
actual filesystem-image initrd at this point, and such systems don't
rely on defconfig anyway.  Drop initrd support (and specifically RAM
block device support) from the defconfigs.

Signed-off-by: Josh Triplett <josh@joshtriplett.org>
---
 arch/x86/configs/i386_defconfig   |    2 --
 arch/x86/configs/x86_64_defconfig |    2 --
 2 files changed, 4 deletions(-)

diff --git a/arch/x86/configs/i386_defconfig b/arch/x86/configs/i386_defconfig
index d833bb6..a6533a2 100644
--- a/arch/x86/configs/i386_defconfig
+++ b/arch/x86/configs/i386_defconfig
@@ -144,8 +144,6 @@ CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
 CONFIG_DEBUG_DEVRES=y
 CONFIG_CONNECTOR=y
 CONFIG_BLK_DEV_LOOP=y
-CONFIG_BLK_DEV_RAM=y
-CONFIG_BLK_DEV_RAM_SIZE=16384
 CONFIG_BLK_DEV_SD=y
 CONFIG_BLK_DEV_SR=y
 CONFIG_BLK_DEV_SR_VENDOR=y
diff --git a/arch/x86/configs/x86_64_defconfig b/arch/x86/configs/x86_64_defconfig
index 7ddcd99..18f3cc4 100644
--- a/arch/x86/configs/x86_64_defconfig
+++ b/arch/x86/configs/x86_64_defconfig
@@ -144,8 +144,6 @@ CONFIG_UEVENT_HELPER_PATH="/sbin/hotplug"
 CONFIG_DEBUG_DEVRES=y
 CONFIG_CONNECTOR=y
 CONFIG_BLK_DEV_LOOP=y
-CONFIG_BLK_DEV_RAM=y
-CONFIG_BLK_DEV_RAM_SIZE=16384
 CONFIG_BLK_DEV_SD=y
 CONFIG_BLK_DEV_SR=y
 CONFIG_BLK_DEV_SR_VENDOR=y
-- 
1.7.10.4


  parent reply	other threads:[~2012-09-03  5:22 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-03  5:20 [PATCH 0/5] x86: Improve defconfigs for use on current systems Josh Triplett
2012-09-03  5:20 ` [PATCH 1/5] x86: Update defconfigs to current results of "make savedefconfig" Josh Triplett
2012-09-05 10:49   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett
2012-09-03  5:21 ` [PATCH 2/5] x86: Switch to ext4 in defconfigs Josh Triplett
2012-09-05 10:50   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett
2012-09-03  5:21 ` [PATCH 3/5] x86: Disable CONFIG_CRC_T10DIF " Josh Triplett
2012-09-05 10:51   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett
2012-09-03  5:21 ` Josh Triplett [this message]
2012-09-05 10:52   ` [tip:x86/build] x86/Kconfig: Turn off CONFIG_BLK_DEV_RAM tip-bot for Josh Triplett
2012-09-03  5:21 ` [PATCH 5/5] x86: Turn off DEBUG_NX_TEST module in defconfigs Josh Triplett
2012-09-05 10:53   ` [tip:x86/build] x86/Kconfig: " tip-bot for Josh Triplett

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=2521e983a63595cd7a331236d929577660f89c72.1346649518.git.josh@joshtriplett.org \
    --to=josh@joshtriplett.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=rdunlap@xenotime.net \
    --cc=suresh.b.siddha@intel.com \
    --cc=tglx@linutronix.de \
    --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).