All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Benjamin Poirier <benjamin.poirier@polymtl.ca>
Cc: ltt-dev@lists.casi.polymtl.ca, linux-kernel@vger.kernel.org
Subject: [RELEASE] LTTng 0.235 for kernel 2.6.36
Date: Tue, 26 Oct 2010 21:10:18 -0400	[thread overview]
Message-ID: <20101027011018.GA28612@Krystal> (raw)
In-Reply-To: <4CC779AE.1040506@polymtl.ca>

* Benjamin Poirier (benjamin.poirier@polymtl.ca) wrote:
> On 25/10/10 10:05 PM, Mathieu Desnoyers wrote:
> > LTTng, the Linux Trace Toolkit Next Generation, is a project that aims at
> > producing a highly efficient full system tracing solution.  It is composed of
> > several components to allow tracing of the kernel, of userspace, trace viewing
> > and analysis and trace streaming.  LTTng is open source software. It is being
> > actively developed with the community.
> > 
> > Changelog:
> > 
> > * Remove duplicated old-napi duplicated device instrumentation.
> 
> There's a tracepoint that went MIA compared to 0.232.

Ah, yes, you are right. There has been quite a few changes in net/core/dev.c
between 2.6.35 and 2.6.36, and it has been especially messy for patch hunks.

LTTng 0.235 fixes this.

Thanks for spotting it!

Mathieu

-- 
Mathieu Desnoyers
Operating System Efficiency R&D Consultant
EfficiOS Inc.
http://www.efficios.com

  reply	other threads:[~2010-10-27  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-26  2:05 [RELEASE] LTTng 0.234 for kernel 2.6.36 Mathieu Desnoyers
2010-10-27  1:00 ` [ltt-dev] " Benjamin Poirier
2010-10-27  1:10   ` Mathieu Desnoyers [this message]
2010-10-28  2:14     ` [RELEASE] LTTng 0.236 " 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=20101027011018.GA28612@Krystal \
    --to=mathieu.desnoyers@efficios.com \
    --cc=benjamin.poirier@polymtl.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ltt-dev@lists.casi.polymtl.ca \
    /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.