From: mathieu.desnoyers@polymtl.ca
To: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org,
Jeremy Fitzhardinge <jeremy@goop.org>,
Steven Rostedt <rostedt@goodmis.org>
Subject: [patch 0/3] Tracepoints kill rcupdate header dependency
Date: Thu, 16 Apr 2009 20:14:37 -0400 [thread overview]
Message-ID: <20090417001437.215128284@polymtl.ca> (raw)
Here is a patch to remove the tracepoint rcupdate dependency by splitting the
read-side primitives of rcupdate.h into a sub rcupdate_defines.h header. That
should make, at least, pvops tracing easier.
It applies on top of current tip/tracing/ftrace tree.
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2009-04-17 0:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-17 0:14 mathieu.desnoyers [this message]
2009-04-17 0:14 ` [patch 1/3] rcupdate header remove whitespace mathieu.desnoyers
2009-04-17 0:14 ` [patch 2/3] RCU move trace defines to rcupdate_defines.h mathieu.desnoyers
2009-04-17 0:43 ` Ingo Molnar
2009-04-17 0:55 ` Mathieu Desnoyers
2009-04-17 1:04 ` Ingo Molnar
2009-04-17 0:14 ` [patch 3/3] tracepoints : remove rcupdate.h dependency mathieu.desnoyers
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=20090417001437.215128284@polymtl.ca \
--to=mathieu.desnoyers@polymtl.ca \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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