From: Nick Andrew <nick@nick-andrew.net>
To: Jason Baron <jbaron@redhat.com>
Cc: akpm@linux-foundation.org, joe@perches.com, greg@kroah.com,
randy.dunlap@oracle.com, linux-kernel@vger.kernel.org
Subject: Re: [patch 0/8] debug printk infrastructure
Date: Fri, 23 May 2008 10:21:01 +1000 [thread overview]
Message-ID: <20080523002101.GC13280@tull.net> (raw)
In-Reply-To: <20080522211331.GA28070@redhat.com>
On Thu, May 22, 2008 at 05:13:31PM -0400, Jason Baron wrote:
> The debugfs file, then lists all the modules that can be 'enabled' for dynamic
> printk calls. Currently, the file has a 4 column format (excerpt from my system:
Nice work Jason.
If you write "enable all" to the debugfs file and then insmod a new
module, will debugging be enabled on the new module?
Nick.
--
PGP Key ID = 0x418487E7 http://www.nick-andrew.net/
PGP Key fingerprint = B3ED 6894 8E49 1770 C24A 67E3 6266 6EB9 4184 87E7
next prev parent reply other threads:[~2008-05-23 0:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-22 21:13 [patch 0/8] debug printk infrastructure Jason Baron
2008-05-23 0:21 ` Nick Andrew [this message]
2008-05-23 16:39 ` Jason Baron
2008-05-27 21:39 ` Andrew Morton
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=20080523002101.GC13280@tull.net \
--to=nick@nick-andrew.net \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=jbaron@redhat.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--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