All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Ellerman <michael@ellerman.id.au>
To: prasad@linux.vnet.ibm.com
Cc: dwilder@us.ibm.com, linux-kernel@vger.kernel.org,
	mathieu.desnoyers@polymtl.ca, hunt@redhat.com,
	dave@linux.vnet.ibm.com
Subject: Re: [RFC Patch 1/1] debugfs_printk and debugfs_dump interface
Date: Mon, 28 Apr 2008 14:54:20 +1000	[thread overview]
Message-ID: <1209358460.8118.12.camel@localhost> (raw)
In-Reply-To: <20080428044854.GA5437@in.ibm.com>

[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]

On Mon, 2008-04-28 at 10:18 +0530, K. Prasad wrote:
> On Mon, Apr 28, 2008 at 10:50:51AM +1000, Michael Ellerman wrote:
> > On Fri, 2008-04-25 at 13:49 +0530, K. Prasad wrote:
> > > On Fri, Apr 25, 2008 at 01:12:00PM +0530, K. Prasad wrote:
> > > > Please find the new patch below.
> > > > > 
> > > Let the email slip through a little early. Please find the revised
> > > patch below.
> > > 
> > > Thanks,
> > > K.Prasad
> > > 
> > > This patch introduces two new interfaces called debugfs_printk and 
> > > debugfs_dump which can be used to print to the debugfs mount directly.
> > > It uses the 'trace' infrastructure underneath and is a patch over it.
> > > A sample file is also created to demonstrate its ease of use.
> > 
> > I still think debugfs_printk() is not the right name, as it is not part
> > of the existing family of debugfs_* routines.

> Whether to call it trace_printk() and trace_dump() is a suggestion I
> would like to ask David Wilder (and others). Let me know if you think
> there are better names.

That would be my pick, given that it's using the trace infrastructure
and it's defined in trace.h, implemented in trace.c, and documented in
trace.txt :)

cheers

-- 
Michael Ellerman
OzLabs, IBM Australia Development Lab

wwweb: http://michael.ellerman.id.au
phone: +61 2 6212 1183 (tie line 70 21183)

We do not inherit the earth from our ancestors,
we borrow it from our children. - S.M.A.R.T Person

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2008-04-28  4:54 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-15 11:14 [RFC Patch 0/1] Enhancements to 'trace' infrastructure K. Prasad
2008-04-15 11:26 ` [RFC Patch 1/1] debugfs_printk and debugfs_dump interface K. Prasad
2008-04-16 21:25   ` David Wilder
2008-04-21 12:43     ` K. Prasad
2008-04-21 17:14       ` Randy Dunlap
2008-04-22  5:22         ` K. Prasad
2008-04-22 14:53           ` Randy Dunlap
2008-04-23  7:59             ` K. Prasad
2008-04-24 21:23       ` David Wilder
2008-04-25  7:42         ` K. Prasad
2008-04-25  8:19           ` K. Prasad
2008-04-28  0:50             ` Michael Ellerman
2008-04-28  4:48               ` K. Prasad
2008-04-28  4:54                 ` Michael Ellerman [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=1209358460.8118.12.camel@localhost \
    --to=michael@ellerman.id.au \
    --cc=dave@linux.vnet.ibm.com \
    --cc=dwilder@us.ibm.com \
    --cc=hunt@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@polymtl.ca \
    --cc=prasad@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.