public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Randy Dunlap <randy.dunlap@oracle.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: Fri, 8 Feb 2008 10:56:31 -0500	[thread overview]
Message-ID: <20080208155631.GC13650@redhat.com> (raw)
In-Reply-To: <20080207132604.ff93b028.randy.dunlap@oracle.com>

On Thu, Feb 07, 2008 at 01:26:04PM -0800, Randy Dunlap wrote:
> > --- 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?
> 

The intention is that pr_debug is off by default. If you pass 'pr_debug' at the
command line, it is turned on early in the boot process. I orginally 
implemented it as pr_debug=<int>, but I believe just the string is simpler.

thanks,

-Jason



      reply	other threads:[~2008-02-08 15:57 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
2008-02-08 15:56   ` Jason Baron [this message]

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