From: Christoph Hellwig <hch@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Christoph Hellwig <hch@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@elte.hu>,
Andrew Morton <akpm@linux-foundation.org>,
Frederic Weisbecker <fweisbec@gmail.com>,
Li Zefan <lizf@cn.fujitsu.com>,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Pekka Enberg <penberg@cs.helsinki.fi>
Subject: Re: [PATCH 1/3] tracing: add __print_flags for events
Date: Wed, 20 May 2009 19:04:13 -0400 [thread overview]
Message-ID: <20090520230413.GA11456@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.00.0905201902060.1080@gandalf.stny.rr.com>
On Wed, May 20, 2009 at 07:02:56PM -0400, Steven Rostedt wrote:
> You mean more like a "__print_enumerated"? A backward translation of
> enumerated types to their names.
Yeah.
> Perhaps __print_symbolic is a bit nicer name.
Sounds good.
next prev parent reply other threads:[~2009-05-20 23:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 21:03 [PATCH 0/3] tracing/events: enumerating flags Steven Rostedt
2009-05-15 21:03 ` [PATCH 1/3] tracing: add __print_flags for events Steven Rostedt
2009-05-18 17:38 ` Christoph Hellwig
2009-05-20 22:13 ` Steven Rostedt
2009-05-20 22:59 ` Christoph Hellwig
2009-05-20 23:02 ` Steven Rostedt
2009-05-20 23:04 ` Christoph Hellwig [this message]
2009-05-21 1:10 ` KOSAKI Motohiro
2009-05-15 21:03 ` [PATCH 2/3] tracing: add previous task state info to sched switch event Steven Rostedt
2009-05-15 21:03 ` [PATCH 3/3] tracing: add flag output for kmem events Steven Rostedt
2009-05-15 21:23 ` Frederic Weisbecker
2009-05-15 21:50 ` Steven Rostedt
2009-05-15 23:40 ` Eduard - Gabriel Munteanu
2009-05-15 23:52 ` Steven Rostedt
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=20090520230413.GA11456@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=eduard.munteanu@linux360.ro \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.org \
/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