From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: Christoph Hellwig <hch@infradead.org>,
Randy Dunlap <randy.dunlap@oracle.com>
Subject: [patch 0/5] Linux Kernel Markers (redux)
Date: Tue, 25 Sep 2007 08:11:45 -0400 [thread overview]
Message-ID: <20070925121145.262664884@polymtl.ca> (raw)
Hi!
Following Christoph's usual nitpicking and Randy's suggestions to put the sample
code in the new samples/ kernel directory, I made modifications to the markers.
The result is that the marker code holds into a single patch; other patches are
for menus, documentation and samples.
Here is the updated version for 2.6.23-rc8-mm1.
It applies in this order:
kconfig-instrumentation.patch
linux-kernel-markers.patch
add-samples-subdir.patch
linux-kernel-markers-samples.patch
linux-kernel-markers-documentation.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
next reply other threads:[~2007-09-25 12:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 12:11 Mathieu Desnoyers [this message]
2007-09-25 12:11 ` [patch 1/5] Combine instrumentation menus in kernel/Kconfig.instrumentation Mathieu Desnoyers
2007-09-25 12:11 ` [patch 2/5] Linux Kernel Markers Mathieu Desnoyers
2007-09-25 12:11 ` [patch 3/5] Add samples subdir Mathieu Desnoyers
2007-09-25 19:00 ` Sam Ravnborg
2007-09-25 20:32 ` Randy Dunlap
2007-09-25 20:40 ` Mathieu Desnoyers
2007-09-25 20:50 ` [patch 3/5] Add samples subdir (updated) Mathieu Desnoyers
2007-09-25 20:58 ` Randy Dunlap
2007-09-25 21:21 ` Randy Dunlap
2007-09-25 21:28 ` [patch 3/5] Add samples subdir Oleg Verych
2007-09-25 12:11 ` [patch 4/5] Linux Kernel Markers - Samples Mathieu Desnoyers
2007-09-25 12:11 ` [patch 5/5] 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=20070925121145.262664884@polymtl.ca \
--to=mathieu.desnoyers@polymtl.ca \
--cc=akpm@linux-foundation.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
/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