All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
To: Stefan Seefeld <stefan_seefeld@mentor.com>
Cc: lttng-dev@lists.lttng.org
Subject: Re: [PATCH lttng-ust] Add trace instrumentation for	some pthread functions.
Date: Wed, 7 Aug 2013 12:12:41 -0400	[thread overview]
Message-ID: <20130807161241.GB1336__18667.8651175045$1375892020$gmane$org@Krystal> (raw)
In-Reply-To: <52026F42.4050005@mentor.com>

* Stefan Seefeld (stefan_seefeld@mentor.com) wrote:
> On 08/07/2013 11:52 AM, Mathieu Desnoyers wrote:
> > * Stefan Seefeld (stefan_seefeld@mentor.com) wrote:
> >> Sorry for the incomplete patch. Here is a corrected one.
> >>
> >> 	Stefan
> > You can add my
> >
> > Acked-by: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
> >
> > To you patch changelog.
> >
> > Can you keep it around and resubmit after we release 2.3-final in a few
> > weeks ?
> 
> Why can't this be comitted to a devel branch, if it isn't fit to go into
> master ?

Because master is currently in feature freeze for the 2.3-rc cycle, and
as a maintainer I'm not keeping any devel/staging branch: this
responsibility currently belongs to the contributors. The new features
flow into master between the end of the release candidate cycle (final
version) and the start of the next rc cycle. See the recent discussion
on the release process on lttng-dev for more details. Feedback is
welcome.

> (Also, does this imply that the malloc patch made it into the
> 2.3 release ?)

Yes, the malloc patch made it into the 2.3 release mainly because it's
fixing incomplete coverage of the already existing malloc/free-related
instrumentation.

The difference with pthread instrumentation is that it's really a new
feature in every possible sense of the term: new kind of library
functions are instrumented, new problems may arise, new files are added,
new shared objects are added. This is exactly what we don't want to add
during rc.

Please note that as soon as you get my acked-by, you can consider this
patch accepted. It's just that we don't have the staging branches to
keep them around, nor the manpower to maintain a 3rd branch in parallel
with the current stable+rc.

Thoughts ?

Thanks,

Mathieu

> 
>     Stefan
> 
> 
> -- 
> Stefan Seefeld
> CodeSourcery / Mentor Graphics
> http://www.mentor.com/embedded-software/
> 
> 
> _______________________________________________
> lttng-dev mailing list
> lttng-dev@lists.lttng.org
> http://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

-- 
Mathieu Desnoyers
EfficiOS Inc.
http://www.efficios.com

  parent reply	other threads:[~2013-08-07 16:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51F97688.30704@mentor.com>
2013-07-31 22:00 ` [PATCH lttng-ust] Add trace instrumentation for some pthread functions Jérémie Galarneau
     [not found] ` <CA+jJMxsoH8Rz6fwZJOPnG-4xvB2w8GO5eqi0JDtHUy7iM-n2WA@mail.gmail.com>
2013-08-01  0:17   ` Stefan Seefeld
     [not found]   ` <51F9A917.9010509@seefeld.name>
2013-08-01  3:16     ` Jérémie Galarneau
2013-08-03  1:28     ` Mathieu Desnoyers
     [not found]     ` <CA+jJMxv4oS0SbMqUF247jS0s0E+6DfdepNT8yHimY=TULHD+tQ@mail.gmail.com>
2013-08-03  1:28       ` Mathieu Desnoyers
     [not found]     ` <20130803012831.GH9033@Krystal>
2013-08-05 13:38       ` Stefan Seefeld
     [not found]       ` <51FFAAD7.3000705@seefeld.name>
2013-08-07  1:32         ` Mathieu Desnoyers
     [not found]         ` <20130807013159.GG19407@Krystal>
2013-08-07 13:14           ` Stefan Seefeld
     [not found]           ` <5202482B.2010705@mentor.com>
2013-08-07 14:05             ` Stefan Seefeld
     [not found]             ` <52025427.5080002@mentor.com>
2013-08-07 14:33               ` Mathieu Desnoyers
     [not found]               ` <20130807143346.GA542@Krystal>
2013-08-07 15:08                 ` Stefan Seefeld
     [not found]                 ` <520262E8.5010106@mentor.com>
2013-08-07 15:19                   ` Mathieu Desnoyers
     [not found]                   ` <20130807151903.GA1035@Krystal>
2013-08-07 15:42                     ` Stefan Seefeld
     [not found]                     ` <52026AD7.7000103@mentor.com>
2013-08-07 15:52                       ` Mathieu Desnoyers
     [not found]                       ` <20130807155228.GC1035@Krystal>
2013-08-07 16:01                         ` Stefan Seefeld
     [not found]                         ` <52026F42.4050005@mentor.com>
2013-08-07 16:12                           ` Mathieu Desnoyers [this message]
     [not found]                           ` <20130807161241.GB1336@Krystal>
2013-08-07 16:25                             ` Stefan Seefeld
     [not found]                             ` <520274F3.3080505@mentor.com>
2013-08-07 16:31                               ` Mathieu Desnoyers
     [not found]                               ` <20130807163153.GA2194@Krystal>
2013-08-07 16:38                                 ` Stefan Seefeld
2013-09-04 14:01                         ` Stefan Seefeld
     [not found]                         ` <52273D4E.5050304@mentor.com>
2013-09-18 14:19                           ` Mathieu Desnoyers
2013-07-31 20:41 Stefan Seefeld

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='20130807161241.GB1336__18667.8651175045$1375892020$gmane$org@Krystal' \
    --to=mathieu.desnoyers@efficios.com \
    --cc=lttng-dev@lists.lttng.org \
    --cc=stefan_seefeld@mentor.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 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.