mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Karim Yaghmour <karim@opersys.com>
To: LTT <ltt@shafik.org>, LTT-Dev <ltt-dev@shafik.org>,
	linux-kernel <linux-kernel@vger.kernel.org>
Subject: [ANNOUNCE] LTT 0.9.6pre4
Date: Tue, 14 Dec 2004 17:32:10 -0500	[thread overview]
Message-ID: <41BF69EA.7050003@opersys.com> (raw)


This is to let everyone know that there's a new LTT release. This
should be the final LTT candidate before I make an official 0.9.6
release, so please test this out and report any problems. This
release includes patches for vanilla 2.6.9, so testing should be
rather straight-forward.

I would like to thank Tim Bird of the CE Linux Forum for going
through the LTT-dev mailing list archives and picking up some of
the contributions that were posted there, and integrating it all.

For this release, I've followed Andrew Morton's advice, and have
proceeded with a namespace cleanup of the kernel code. So,
instead of trace statements being like this:
	TRACE_SCHEDCHANGE(prev, next);
they have the more mainstream form of:
	ltt_ev_schedchange(prev, next);

Here are the highlights of the most important additions since the
opening of the 0.9.6preX branch:
     * Lockless logging (relayfs)
     * Per-CPU buffering
     * TSC timestamping
     * Use of relayfs for buffering and user-space interfacing
     * Code cleanup for adhering to kernel coding standards
     * ARM port

Enjoy,

Karim Yaghmour
-- 
Author, Speaker, Developer, Consultant
Pushing Embedded and Real-Time Linux Systems Beyond the Limits
http://www.opersys.com || karim@opersys.com || 1-866-677-4546

                 reply	other threads:[~2004-12-14 22:28 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=41BF69EA.7050003@opersys.com \
    --to=karim@opersys.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@shafik.org \
    --cc=ltt@shafik.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

Powered by JetHome