public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: linux-kernel@vger.kernel.org
Cc: Linus Torvalds <torvalds@osdl.org>,
	  Andrew Morton <akpm@osdl.org>, Ingo Molnar <mingo@redhat.com>,
	  Greg Kroah-Hartman <gregkh@suse.de>,
	  Christoph Hellwig <hch@infradead.org>,
	ltt-dev@shafik.org,   systemtap@sources.redhat.com,
	Douglas Niehaus <niehaus@eecs.ku.edu>,
	  Thomas Gleixner <tglx@linutronix.de>
Subject: [PATCH 00/05] Linux Kernel Markers
Date: Fri, 12 Jan 2007 00:02:00 -0000	[thread overview]
Message-ID: <11685601382063-git-send-email-mathieu.desnoyers@polymtl.ca> (raw)

Hi,

You will find, in the following posts, the latest revision of the Linux Kernel
Markers. Due to the need some tracing projects (LTTng, SystemTAP) has of this
kind of mechanism, it could be nice to consider it for mainstream inclusion.

The following patches apply on 2.6.20-rc4-git3.

Signed-off-by : Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>

             reply	other threads:[~2007-01-12  0:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-12  0:02 Mathieu Desnoyers [this message]
2007-01-12  0:07 ` [PATCH 03/05] Linux Kernel Markers : powerpc optimisation Mathieu Desnoyers
2007-01-12  0:07 ` [PATCH 02/05] Linux Kernel Markers, architecture independant code Mathieu Desnoyers
2007-01-12  0:12 ` [PATCH 05/05] Linux Kernel Markers, non optimised architectures Mathieu Desnoyers
2007-01-12  4:39   ` Nick Piggin
2007-01-12  5:05     ` Mathieu Desnoyers
2007-01-12  5:10       ` Nick Piggin
2007-01-12 17:20         ` Mathieu Desnoyers
2007-01-12 17:43           ` Mathieu Desnoyers
2007-01-12 18:23         ` [PATCH 05/05] update - " Mathieu Desnoyers
2007-01-12  0:12 ` [PATCH 01/05] Linux Kernel Markers : Kconfig menus Mathieu Desnoyers
2007-01-12  0:42 ` [PATCH 04/05] Linux Kernel Markers : i386 optimisation 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=11685601382063-git-send-email-mathieu.desnoyers@polymtl.ca \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=akpm@osdl.org \
    --cc=gregkh@suse.de \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.org \
    --cc=mingo@redhat.com \
    --cc=niehaus@eecs.ku.edu \
    --cc=systemtap@sources.redhat.com \
    --cc=tglx@linutronix.de \
    --cc=torvalds@osdl.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).