public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: landley@trommello.org
Cc: linux-kernel@vger.kernel.org, boissiere@nl.linux.org
Subject: Re: Crunch time -- Final merge candidates for 3.0 (the list).
Date: Mon, 21 Oct 2002 02:03:48 -0400	[thread overview]
Message-ID: <3DB398C4.6DB5CB0B@opersys.com> (raw)
In-Reply-To: 200210201849.23667.landley@trommello.org


Rob Landley wrote:
> o Ready - Build option for Linux Trace Toolkit (LTT) (Karim Yaghmour)
> http://www.uwsg.iu.edu/hypermail/linux/kernel/0204.1/0832.html

LTT has seen a number of changes since the posting above. Mainly,
we've followed the recommendations of quite a few folks from the LKML.
Here are some highlights summarizing the changes:
http://marc.theaimsgroup.com/?l=linux-kernel&m=103491640202541&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=103423004321305&w=2
http://marc.theaimsgroup.com/?l=linux-kernel&m=103247532007850&w=2

The latest patch is available here:
http://opersys.com/ftp/pub/LTT/ExtraPatches/patch-ltt-linux-2.5.44-vanilla-021019-2.2.bz2
Use this patch with version 0.9.6pre2 of the user tools:
http://opersys.com/ftp/pub/LTT/TraceToolkit-0.9.6pre2.tgz

Karim

===================================================
                 Karim Yaghmour
               karim@opersys.com
      Embedded and Real-Time Linux Expert
===================================================

  parent reply	other threads:[~2002-10-21  5:52 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-20 23:49 Crunch time -- Final merge candidates for 3.0 (the list) Rob Landley
2002-10-21  5:44 ` Hans Reiser
2002-10-21  6:03 ` Karim Yaghmour [this message]
2002-10-21  1:37   ` Rob Landley
2002-10-21  6:43     ` Andreas Dilger
2002-10-21  2:47       ` Rob Landley
2002-10-21  8:05         ` Andreas Dilger
2002-10-21  8:25         ` Andrew Morton
2002-10-21 11:56 ` Alan Cox
2002-10-21 12:23 ` Denis Vlasenko
2002-10-21  3:00   ` Rob Landley

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=3DB398C4.6DB5CB0B@opersys.com \
    --to=karim@opersys.com \
    --cc=boissiere@nl.linux.org \
    --cc=landley@trommello.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