public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jason Baron <jbaron@redhat.com>
To: Nick Andrew <nick@nick-andrew.net>
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 12:39:22 -0400	[thread overview]
Message-ID: <20080523163922.GA21027@redhat.com> (raw)
In-Reply-To: <20080523002101.GC13280@tull.net>

On Fri, May 23, 2008 at 10:21:01AM +1000, Nick Andrew wrote:
> If you write "enable all" to the debugfs file and then insmod a new
> module, will debugging be enabled on the new module?
> 

currently, no. i did it that way to make the implementation simpler.

however, i think the "enable all" should enable debugging for a subsequent
'insmod'. added to the todo list.

thanks,

-Jason

  reply	other threads:[~2008-05-23 16:40 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
2008-05-23 16:39   ` Jason Baron [this message]
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=20080523163922.GA21027@redhat.com \
    --to=jbaron@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=greg@kroah.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