From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [patch 0/5] Linux Kernel Markers
Date: Fri, 15 Jun 2007 16:29:59 -0400 [thread overview]
Message-ID: <20070615202959.316963297@polymtl.ca> (raw)
Hi,
This is the latest release of the Linux Kernel Markers, adapted to use the new
"immediate values" infrastructure to provide low impact when compiled-in but
disabled.
It applies at the end of the 2.6.22-rc4-mm2 series, after the "immediate values"
patches, in this order:
use-extra_rwdata-in-architectures.patch
#
linux-kernel-markers-architecture-independent-code.patch
linux-kernel-markers-kconfig-menus.patch
linux-kernel-markers-documentation.patch
linux-kernel-markers-port-blktrace-to-markers.patch
Regards,
Mathieu
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next reply other threads:[~2007-06-15 20:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 20:29 Mathieu Desnoyers [this message]
2007-06-15 20:30 ` [patch 1/5] Use EXTRARW_DATA in architectures Mathieu Desnoyers
2007-06-15 21:55 ` Sam Ravnborg
2007-06-17 2:28 ` [PATCH] Use DATA_DATA in cris Mathieu Desnoyers
2007-06-17 2:29 ` [PATCH] Add missing DATA_DATA to powerpc Mathieu Desnoyers
2007-06-17 2:29 ` [PATCH] Use DATA_DATA in xtensa Mathieu Desnoyers
2007-06-17 2:30 ` [patch 1/5] Use EXTRARW_DATA in architectures Mathieu Desnoyers
2007-06-15 20:30 ` [patch 2/5] Linux Kernel Markers, architecture independent code Mathieu Desnoyers
2007-06-15 20:30 ` [patch 3/5] Linux Kernel Markers - Add kconfig menus for the marker code Mathieu Desnoyers
2007-06-15 20:30 ` [patch 4/5] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-06-15 20:30 ` [patch 5/5] Port of blktrace to the Linux Kernel Markers 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=20070615202959.316963297@polymtl.ca \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.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