From: Byron Bradley <byron.bbradley@gmail.com>
To: linux-arm-kernel@lists.arm.linux.org.uk
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
Byron Bradley <byron.bbradley@gmail.com>,
Nick Piggin <npiggin@suse.de>,
Russell King <rmk@arm.linux.org.uk>
Subject: [PATCH] ramdisk driver: make rd_size non-static
Date: Fri, 18 Jan 2008 02:02:17 +0000 [thread overview]
Message-ID: <1200621737-1458-1-git-send-email-byron.bbradley@gmail.com> (raw)
In arch/arm/kernel/setup.c:setup_ramdisk(), rd_size is set from the
boot tags. The replacement ramdisk driver has rd_size as static
which causes linking to fail when ramdisk is built-in.
Signed-off-by: Byron Bradley <byron.bbradley@gmail.com>
Cc: Nick Piggin <npiggin@suse.de>
Cc: Russell King <rmk@arm.linux.org.uk>
---
This patch applies against 2.6.24-rc8-mm1 and has not been tested,
it is only know to compile. I'm not sure if there is a better way
to set rd_size or if this is OK.
drivers/block/brd.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/block/brd.c b/drivers/block/brd.c
index 5ef1d26..8536480 100644
--- a/drivers/block/brd.c
+++ b/drivers/block/brd.c
@@ -385,7 +385,7 @@ static struct block_device_operations brd_fops = {
* And now the modules code and kernel interface.
*/
static int rd_nr;
-static int rd_size = CONFIG_BLK_DEV_RAM_SIZE;
+int rd_size = CONFIG_BLK_DEV_RAM_SIZE;
module_param(rd_nr, int, 0);
MODULE_PARM_DESC(rd_nr, "Maximum number of brd devices");
module_param(rd_size, int, 0);
--
1.5.4.rc2.38.gd6da3
next reply other threads:[~2008-01-18 2:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-18 2:02 Byron Bradley [this message]
2008-01-18 2:28 ` Andrew Morton
2008-01-18 2:39 ` Matt Mackall
2008-01-18 11:29 ` Nick Piggin
2008-01-18 19:28 ` Russell King - ARM Linux
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=1200621737-1458-1-git-send-email-byron.bbradley@gmail.com \
--to=byron.bbradley@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=rmk@arm.linux.org.uk \
/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
all inboxes | Powered by JetHome®