public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: Fabian Frederick <fabf@skynet.be>, linux-kernel@vger.kernel.org
Cc: npiggin@gmail.com
Subject: Re: [PATCH 1/1] ramdisk: documentation update
Date: Sat, 07 Dec 2013 19:19:11 -0800	[thread overview]
Message-ID: <52A3E52F.1090303@infradead.org> (raw)
In-Reply-To: <20131207075221.5401d0c4fdebe5515c4f1643@skynet.be>

On 12/06/13 15:52, Fabian Frederick wrote:
> -ramdisk_blocksize doesn't exist anymore.
> -Module parameters added to documentation.
> 
> Signed-off-by: Fabian Frederick <fabf@skynet.be>
> ---
>  Documentation/blockdev/ramdisk.txt | 23 ++++++++++++++++++-----
>  1 file changed, 18 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/blockdev/ramdisk.txt b/Documentation/blockdev/ramdisk.txt
> index fa72e97..5dca7b1 100644
> --- a/Documentation/blockdev/ramdisk.txt
> +++ b/Documentation/blockdev/ramdisk.txt
> @@ -36,21 +36,30 @@ allowing one to squeeze more programs onto an average installation or
>  rescue floppy disk.
>  
>  
> -2) Kernel Command Line Parameters
> +2) Parameters
>  ---------------------------------
>  
> +2a) Kernel Command Line Parameters
> +
>  	ramdisk_size=N
>  	==============
>  
>  This parameter tells the RAM disk driver to set up RAM disks of N k size.  The
>  default is 4096 (4 MB) (8192 (8 MB) on S390).

I don't find any place that S390 changes CONFIG_BLK_DEV_RAM_SIZE from its default
of 4096 to 8192.  Did you?  If so, where please?


>  
> -	ramdisk_blocksize=N
> -	===================
> +2b) Module parameters
> +
> +	rd_nr
> +	=====
> +	/dev/ramX devices created.
>  
> -This parameter tells the RAM disk driver how many bytes to use per block.  The
> -default is 1024 (BLOCK_SIZE).
> +	max_part
> +	========
> +	Maximum partition number.
>  
> +	rd_size
> +	=======
> +	cf ramdisk_size.

Compare to ramdisk_size?  how about

	See ramdisk_size.
or
	Same as ramdisk_size.

>  
>  3) Using "rdev -r"
>  ------------------


As for the Changelog, it would be better just to delete all of it.
That's what git is for (and good at).


-- 
~Randy

  reply	other threads:[~2013-12-08  3:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-06 23:52 [PATCH 1/1] ramdisk: documentation update Fabian Frederick
2013-12-08  3:19 ` Randy Dunlap [this message]
2013-12-08  8:35   ` Fabian Frederick
2013-12-08 17:21     ` Randy Dunlap
  -- strict thread matches above, loose matches on Subject: below --
2013-12-08 11:28 Fabian Frederick
2013-12-09  3:59 ` 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=52A3E52F.1090303@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=fabf@skynet.be \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npiggin@gmail.com \
    /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