From: Christoph Hellwig <hch@infradead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
Cc: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: Re: [patch 3/4] Linux Kernel Markers - Documentation
Date: Tue, 28 Aug 2007 21:53:14 +0100 [thread overview]
Message-ID: <20070828205314.GA10549@infradead.org> (raw)
In-Reply-To: <20070820202759.645867202@polymtl.ca>
On Mon, Aug 20, 2007 at 04:27:07PM -0400, Mathieu Desnoyers wrote:
> Here is some documentation explaining what is/how to use the Linux
> Kernel Markers.
While porting my code from an older markers version I noticed the
marker callbacks have grown a void *private argument. Add it to
the documentation aswell.
Signed-off-by: Christoph Hellwig <hch@lst.de>
Index: linux-2.6/Documentation/marker.txt
===================================================================
--- linux-2.6.orig/Documentation/marker.txt 2007-08-28 22:50:37.000000000 +0200
+++ linux-2.6/Documentation/marker.txt 2007-08-28 22:51:07.000000000 +0200
@@ -115,7 +115,7 @@ struct probe_data {
};
void probe_subsystem_event(const struct __mark_marker *mdata,
- const char *format, ...)
+ void *private, const char *format, ...)
{
va_list ap;
/* Declare args */
next prev parent reply other threads:[~2007-08-28 20:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-20 20:27 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-08-20 20:27 ` [patch 1/4] Linux Kernel Markers - Architecture Independent Code Mathieu Desnoyers
2007-08-21 0:43 ` Rusty Russell
2007-08-24 16:26 ` Mathieu Desnoyers
2007-08-25 20:49 ` Rusty Russell
2007-08-25 21:26 ` Mathieu Desnoyers
2007-08-20 20:27 ` [patch 2/4] Linux Kernel Markers - Add kconfig menus for the marker code Mathieu Desnoyers
2007-08-20 20:27 ` [patch 3/4] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-08-28 20:53 ` Christoph Hellwig [this message]
2007-08-28 21:24 ` Mathieu Desnoyers
2007-08-20 20:27 ` [patch 4/4] Port of blktrace to the Linux Kernel Markers Mathieu Desnoyers
-- strict thread matches above, loose matches on Subject: below --
2007-09-18 21:13 [patch 0/4] Linux Kernel Markers for 2.6.23-rc6-mm1 Mathieu Desnoyers
2007-09-18 21:13 ` [patch 3/4] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-09-18 23:22 ` Randy Dunlap
2007-09-19 11:18 ` Mathieu Desnoyers
2007-09-17 18:46 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-09-17 18:46 ` [patch 3/4] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-08-27 16:05 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-08-27 16:05 ` [patch 3/4] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-08-12 15:10 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-08-12 15:10 ` [patch 3/4] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-08-12 20:11 ` Frank Ch. Eigler
2007-08-17 15:56 ` Mathieu Desnoyers
2007-07-14 1:29 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-07-14 1:29 ` [patch 3/4] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-07-03 17:08 [patch 0/4] Linux Kernel Markers Mathieu Desnoyers
2007-07-03 17:08 ` [patch 3/4] Linux Kernel Markers - Documentation 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=20070828205314.GA10549@infradead.org \
--to=hch@infradead.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
/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