From: Andrew Morton <akpm@linux-foundation.org>
To: Jason Baron <jbaron@redhat.com>
Cc: joe@perches.com, greg@kroah.com, nick@nick-andrew.net,
randy.dunlap@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/8] debug printk infrastructure -dynamic printk docs
Date: Tue, 27 May 2008 14:40:28 -0700 [thread overview]
Message-ID: <20080527144028.83f87adc.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080522211723.GE28070@redhat.com>
On Thu, 22 May 2008 17:17:23 -0400
Jason Baron <jbaron@redhat.com> wrote:
>
> 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 bf6303e..d9a1245 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -1580,6 +1580,11 @@ and is between 256 and 4096 characters. It is defined in the file
> autoconfiguration.
> Ranges are in pairs (memory base and size).
>
> + dynamic_printk
> + Enables pr_debug()/dev_dbg() calls if
> + CONFIG_PRINK_DYNAMIC has been enabled. These can also
> + be switched on/off via <debugfs>/dynamic_printk/modules
> +
There is no CONFIG_PRINK_DYNAMIC? I guess you meant
CONFIG_DYNAMIC_PRINTK_DEBUG.
> print-fatal-signals=
> [KNL] debug: print fatal signals
> print-fatal-signals=1: print segfault info to
> --
> 1.5.4.5
>
prev parent reply other threads:[~2008-05-27 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 21:17 [PATCH 4/8] debug printk infrastructure -dynamic printk docs Jason Baron
2008-05-27 21:40 ` Andrew Morton [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=20080527144028.83f87adc.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=jbaron@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nick@nick-andrew.net \
--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