public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Jason Baron <jbaron@redhat.com>
Cc: mathieu.desnoyers@polymtl.ca, akpm@linux-foundation.org,
	mingo@elte.hu, fche@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 4/4] make pr_debug() dynamic - update docs
Date: Thu, 7 Feb 2008 13:26:04 -0800	[thread overview]
Message-ID: <20080207132604.ff93b028.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20080207211349.GF14732@redhat.com>

On Thu, 7 Feb 2008 16:13:49 -0500 Jason Baron wrote:

> 
> -add documentation about pr_debug kernel-parameters.txt
> 
> Signed-off-by: Jason Baron <jbaron@redhat.com>
> ---
> 
>  Documentation/kernel-parameters.txt |    5 +++++
>  1 files changed, 5 insertions(+), 0 deletions(-)
> 
> 
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index cf38689..6d524bb 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -1494,6 +1494,11 @@ and is between 256 and 4096 characters. It is defined in the file
>  			autoconfiguration.
>  			Ranges are in pairs (memory base and size).
>  
> +	pr_debug
> +			Enables pr_debug() calls if the immediate
> +			infrastructure has been enabled. These can also be
> +			switched on/off via /proc/sys/debug/pr_debug.

Is this actually Enables/disables?
I.e., is this actually pr_debug=<int> ?
If so, please document that also.  If not, why not?

>  	print-fatal-signals=
>  			[KNL] debug: print fatal signals
>  			print-fatal-signals=1: print segfault info to



---
~Randy

  reply	other threads:[~2008-02-07 21:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-07 21:13 [patch 4/4] make pr_debug() dynamic - update docs Jason Baron
2008-02-07 21:26 ` Randy Dunlap [this message]
2008-02-08 15:56   ` Jason Baron

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=20080207132604.ff93b028.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=fche@redhat.com \
    --cc=jbaron@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=mingo@elte.hu \
    /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