All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gerd Knorr <kraxel@bytesex.org>
To: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	uml devel <user-mode-linux-devel@lists.sourceforge.net>,
	Jeff Dike <jdike@addtoit.com>,
	Blaisorblade <blaisorblade_spam@yahoo.it>
Subject: [uml-devel] [patch] uml: ramdisk config fix
Date: Tue, 7 Dec 2004 15:35:41 +0100	[thread overview]
Message-ID: <20041207143541.GA23555@bytesex> (raw)

ObviouslyCorrect[tm] buildfix ;)
Should go into 2.6.10.

Signed-off-by: Gerd Knorr <kraxel@bytesex.org>
---
 arch/um/Kconfig_block |    4 ++++
 1 files changed, 4 insertions(+)

Index: linux-2.6.10-rc3/arch/um/Kconfig_block
===================================================================
--- linux-2.6.10-rc3.orig/arch/um/Kconfig_block	2004-12-07 12:12:09.000000000 +0100
+++ linux-2.6.10-rc3/arch/um/Kconfig_block	2004-12-07 13:41:38.692103167 +0100
@@ -43,6 +43,10 @@ config BLK_DEV_NBD
 config BLK_DEV_RAM
 	tristate "RAM disk support"
 
+config BLK_DEV_RAM_COUNT
+	int "Default number of RAM disks" if BLK_DEV_RAM
+	default "16"
+
 config BLK_DEV_RAM_SIZE
 	int "Default RAM disk size"
 	depends on BLK_DEV_RAM

-- 
#define printk(args...) fprintf(stderr, ## args)


-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

WARNING: multiple messages have this Message-ID (diff)
From: Gerd Knorr <kraxel@bytesex.org>
To: Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	uml devel <user-mode-linux-devel@lists.sourceforge.net>,
	Jeff Dike <jdike@addtoit.com>,
	Blaisorblade <blaisorblade_spam@yahoo.it>
Subject: [patch] uml: ramdisk config fix
Date: Tue, 7 Dec 2004 15:35:41 +0100	[thread overview]
Message-ID: <20041207143541.GA23555@bytesex> (raw)

ObviouslyCorrect[tm] buildfix ;)
Should go into 2.6.10.

Signed-off-by: Gerd Knorr <kraxel@bytesex.org>
---
 arch/um/Kconfig_block |    4 ++++
 1 files changed, 4 insertions(+)

Index: linux-2.6.10-rc3/arch/um/Kconfig_block
===================================================================
--- linux-2.6.10-rc3.orig/arch/um/Kconfig_block	2004-12-07 12:12:09.000000000 +0100
+++ linux-2.6.10-rc3/arch/um/Kconfig_block	2004-12-07 13:41:38.692103167 +0100
@@ -43,6 +43,10 @@ config BLK_DEV_NBD
 config BLK_DEV_RAM
 	tristate "RAM disk support"
 
+config BLK_DEV_RAM_COUNT
+	int "Default number of RAM disks" if BLK_DEV_RAM
+	default "16"
+
 config BLK_DEV_RAM_SIZE
 	int "Default RAM disk size"
 	depends on BLK_DEV_RAM

-- 
#define printk(args...) fprintf(stderr, ## args)

             reply	other threads:[~2004-12-07 15:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-07 14:35 Gerd Knorr [this message]
2004-12-07 14:35 ` [patch] uml: ramdisk config fix Gerd Knorr

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=20041207143541.GA23555@bytesex \
    --to=kraxel@bytesex.org \
    --cc=akpm@osdl.org \
    --cc=blaisorblade_spam@yahoo.it \
    --cc=jdike@addtoit.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.