From: walter harms <wharms@bfs.de>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] RAMDISK: Remove long-deprecated "ramdisk=" boot-time
Date: Thu, 07 May 2009 07:16:51 +0000 [thread overview]
Message-ID: <4A028AE3.8050107@bfs.de> (raw)
In-Reply-To: <alpine.LFD.2.00.0905061821260.26544@localhost.lan>
Robert P. J. Day schrieb:
> The "ramdisk" parameter was removed from the defunct rd.c file quite
> some time ago, in favour of the more specific "ramdisk_size"
> parameter so, for consistency, the same should be done here.
>
> Signed-off-by: Robert P. J. Day <rpjday@crashcourse.ca>
>
> ---
>
> the earlier removal was in fac8b209b1084bc85748bd54e13d00c1262b220f.
>
> diff --git a/drivers/block/brd.c b/drivers/block/brd.c
> index 5f7e64b..4bf8705 100644
> --- a/drivers/block/brd.c
> +++ b/drivers/block/brd.c
> @@ -407,12 +407,7 @@ static int __init ramdisk_size(char *str)
> rd_size = simple_strtol(str, NULL, 0);
> return 1;
> }
> -static int __init ramdisk_size2(char *str)
> -{
> - return ramdisk_size(str);
> -}
> -__setup("ramdisk=", ramdisk_size);
> -__setup("ramdisk_size=", ramdisk_size2);
> +__setup("ramdisk_size=", ramdisk_size);
> #endif
>
> /*
>
i do not use this parameter but people will be confused if it suddenly vanish.
IMHO it would be better to add something like
printk(KERN_ERR "'ramdisk=' will be removed with kernel 2.6.35 ....";
pleae note there is a clear kernel number what will put pressure on everyone
really to remove the parameter.
just my two cents,
wh
next prev parent reply other threads:[~2009-05-07 7:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-06 22:23 [PATCH] RAMDISK: Remove long-deprecated "ramdisk=" boot-time Robert P. J. Day
2009-05-07 7:16 ` walter harms [this message]
2009-05-07 8:56 ` Robert P. J. Day
2009-05-12 5:09 ` [PATCH] RAMDISK: Remove long-deprecated "ramdisk=" boot-time param Nick Piggin
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=4A028AE3.8050107@bfs.de \
--to=wharms@bfs.de \
--cc=kernel-janitors@vger.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