From: Ingo Molnar <mingo@elte.hu>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Frederic Weisbecker <fweisbec@gmail.com>,
Zhaolei <zhaolei@cn.fujitsu.com>,
Tom Zanussi <tzanussi@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] tracing, boottrace: Move include/trace/boot.h to include/linux/boottrace.h
Date: Tue, 14 Apr 2009 01:40:27 +0200 [thread overview]
Message-ID: <20090413234027.GH817@elte.hu> (raw)
In-Reply-To: <alpine.DEB.2.00.0904131933110.3041@gandalf.stny.rr.com>
* Steven Rostedt <rostedt@goodmis.org> wrote:
> On Tue, 14 Apr 2009, Ingo Molnar wrote:
> >
> > The sane thing would be to put event headers into
> > include/trace/events/ and put more generic/utility headers into
> > include/trace/.
> >
> > Reserving a full subdirectory for one singular purpose is a needless
> > waste of a nice (and unique) name-space resource.
>
> That's fine with me too. I just want the trace points to be easily
> seen. But by making a sub directory, wont we need to have all
> users of tracepoints do something like:
>
> #include <trace/events/sched.h>
>
> That might be fine too.
Yes - it would allow the dropping of the annoyingly repetitive
_event string from those definition files as well?
Ingo
next prev parent reply other threads:[~2009-04-13 23:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-13 3:54 [PATCH 1/2] tracing, boottrace: Move include/trace/boot.h to include/linux/boottrace.h Zhaolei
2009-04-13 3:55 ` [PATCH 2/2] tracing, syscalltrace: Move include/trace/syscall.h to include/linux/syscalltrace.h Zhaolei
2009-04-13 14:28 ` Frederic Weisbecker
2009-04-13 14:25 ` [PATCH 1/2] tracing, boottrace: Move include/trace/boot.h to include/linux/boottrace.h Frederic Weisbecker
2009-04-13 22:24 ` Ingo Molnar
2009-04-13 23:11 ` Steven Rostedt
2009-04-13 23:28 ` Ingo Molnar
2009-04-13 23:34 ` Steven Rostedt
2009-04-13 23:40 ` Ingo Molnar [this message]
2009-04-13 23:51 ` Steven Rostedt
2009-04-13 23:53 ` Ingo Molnar
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=20090413234027.GH817@elte.hu \
--to=mingo@elte.hu \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tzanussi@gmail.com \
--cc=zhaolei@cn.fujitsu.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