public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: Jason Baron <jbaron@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [patch 1/3] dynamic printk - core infrastructure
Date: Tue, 01 Apr 2008 19:07:24 -0700	[thread overview]
Message-ID: <1207102044.23161.163.camel@localhost> (raw)
In-Reply-To: <20080401144744.d0d10504.randy.dunlap@oracle.com>

On Tue, 2008-04-01 at 14:47 -0700, Randy Dunlap wrote:
> > echo "add file.c" > /sys/kernel/debug/dynamic_printk/files
> > echo "remove file.c" > /sys/kernel/debug/dynamic_printk/files

I think this would be better by module rather than filename.
KBUILD_MODNAME would be a better choice.



  reply	other threads:[~2008-04-02  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 19:49 [patch 1/3] dynamic printk - core infrastructure Jason Baron
2008-04-01 20:09 ` mws
2008-04-01 21:47 ` Randy Dunlap
2008-04-02  2:07   ` Joe Perches [this message]
2008-04-02 18:21     ` Jason Baron
2008-04-02 18:58       ` Joe Perches
2008-04-04 18:13         ` Jason Baron
2008-04-04 18:33           ` Joe Perches

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=1207102044.23161.163.camel@localhost \
    --to=joe@perches.com \
    --cc=jbaron@redhat.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