All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: akpm@linux-foundation.org, linux-kernel@vger.kernel.org
Cc: Haavard Skinnemoen <hskinnemoen@atmel.com>
Subject: [patch 0/4] Instrumentation menu removal
Date: Tue, 04 Dec 2007 12:43:58 -0500	[thread overview]
Message-ID: <20071204174358.271253130@polymtl.ca> (raw)

Hi Andrew,

Here is the instrumentation menu removal patchset, updated to take care of
recent avr32 changes. It has been done on top of 2.6.24-rc4 with the following
patches applied :

[PATCH 1/2] [AVR32] Include instrumentation menu
[PATCH 2/2] [AVR32] Oprofile support

(which have been merged in the avr32 tree by Haavard)

Applying it in the current -mm after the "git-avr32.patch" in the following
order should work fine :

add-kconfig-to-arch.patch
add-have-oprofile.patch
add-have-kprobes.patch
move-kconfig-instrumentation-to-arch.patch

If you have any problem applying them, just tell me. I think there is no
difference between 2.6.24-rc4 + those two patches and your tree in that aspect,
but if there happen to be one, I'll get a -mm tree and do a clean patchset.

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-12-04 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 17:43 Mathieu Desnoyers [this message]
2007-12-04 17:43 ` [patch 1/4] Create arch/Kconfig Mathieu Desnoyers
2007-12-04 17:44 ` [patch 2/4] Add HAVE_OPROFILE Mathieu Desnoyers
2007-12-04 17:44 ` [patch 3/4] Add HAVE_KPROBES Mathieu Desnoyers
2007-12-04 17:44 ` [patch 4/4] Move Kconfig.instrumentation to arch/Kconfig and init/Kconfig Mathieu Desnoyers
2007-12-04 18:03 ` [patch 0/4] Instrumentation menu removal Haavard Skinnemoen
  -- strict thread matches above, loose matches on Subject: below --
2007-11-13 14:26 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=20071204174358.271253130@polymtl.ca \
    --to=mathieu.desnoyers@polymtl.ca \
    --cc=akpm@linux-foundation.org \
    --cc=hskinnemoen@atmel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.