LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: "Ahmed S. Darwish" <darwish.07@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>, linux-doc@vger.kernel.org
Subject: [PATCH] Documentation: log_buf_len accepts [KMG]
Date: Sun, 6 Feb 2011 20:40:02 -0800	[thread overview]
Message-ID: <20110206204002.2f3eab4e.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20110206174504.GA23024@laptop>

From: Randy Dunlap <randy.dunlap@oracle.com>

Update the "log_buf_len" description to use [KMG] syntax for the
buffer size.

Signed-off-by: Randy Dunlap <randy.dunlap@oracle.com>
---
 Documentation/kernel-parameters.txt |    7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

--- linux-next-20110204.orig/Documentation/kernel-parameters.txt
+++ linux-next-20110204/Documentation/kernel-parameters.txt
@@ -1262,10 +1262,9 @@ and is between 256 and 4096 characters. 
 			6 (KERN_INFO)		informational
 			7 (KERN_DEBUG)		debug-level messages
 
-	log_buf_len=n	Sets the size of the printk ring buffer, in bytes.
-			Format: { n | nk | nM }
-			n must be a power of two.  The default size
-			is set in the kernel config file.
+	log_buf_len=n[KMG]	Sets the size of the printk ring buffer,
+			in bytes.  n must be a power of two.  The default
+			size is set in the kernel config file.
 
 	logo.nologo	[FB] Disables display of the built-in Linux logo.
 			This may be used to provide more screen space for

  reply	other threads:[~2011-02-07  4:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 17:45 [PATCH -next] Documentation: Explain the [KMG] parameters suffix Ahmed S. Darwish
2011-02-07  4:40 ` Randy Dunlap [this message]
2011-02-07 11:40   ` [PATCH] Documentation: log_buf_len accepts [KMG] Ahmed S. Darwish
2011-02-07 15:51     ` 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=20110206204002.2f3eab4e.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=darwish.07@gmail.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --subject='Re: [PATCH] Documentation: log_buf_len accepts [KMG]' \
    /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

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).