public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Subject: [patch 0/6] Linux Kernel Markers - for 2.6.22-rc2-mm1
Date: Wed, 30 May 2007 10:03:59 -0400	[thread overview]
Message-ID: <20070530140359.006540666@polymtl.ca> (raw)

Hi,

Here is the port of the Linux Kernel Markers for 2.6.22-rc2-mm1. It depends on
the conditional calls infrastructure.

I took account of Sam Ravnborg's comments about EXTRARW_DATA in this patch.

It applies at the end of the 2.6.22-rc2-mm1 series, after the conditional call
patches, in the following order :

use-extra_rwdata-in-architectures.patch
linux-kernel-markers-architecture-independent-code.patch
linux-kernel-markers-hash-table.patch
linux-kernel-markers-kconfig-menus.patch
linux-kernel-markers-documentation.patch
linux-kernel-markers-port-blktrace-to-markers.patch

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

             reply	other threads:[~2007-05-30 14:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-30 14:03 Mathieu Desnoyers [this message]
2007-05-30 14:04 ` [patch 1/6] Use EXTRARW_DATA in architectures Mathieu Desnoyers
2007-05-30 14:04 ` [patch 2/6] Linux Kernel Markers, architecture independent code Mathieu Desnoyers
2007-05-30 14:04 ` [patch 3/6] Linux Kernel Markers - Hash Table Mathieu Desnoyers
2007-05-30 14:04 ` [patch 4/6] Linux Kernel Markers - Add kconfig menus for the marker code Mathieu Desnoyers
2007-05-30 14:04 ` [patch 5/6] Linux Kernel Markers - Documentation Mathieu Desnoyers
2007-05-30 14:04 ` [patch 6/6] 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=20070530140359.006540666@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