lttng-dev.lists.lttng.org archive mirror
 help / color / mirror / Atom feed
From: Michael Jeanson <mjeanson@efficios.com>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
	Florian Walbroel <walbroel@silexica.com>
Cc: Julien Desfossez <ju@klipix.org>, lttng-dev <lttng-dev@lists.lttng.org>
Subject: Re: Fwd: [PATCH lttng-modules] Add UDP and ICMP packet header information to the tracepoint:
Date: Tue, 17 Dec 2019 12:20:46 -0500	[thread overview]
Message-ID: <88c1b057-e920-433e-77b0-03dd04cd14de__35412.5898958714$1576603271$gmane$org@efficios.com> (raw)
In-Reply-To: <1666401048.8323.1576593591017.JavaMail.zimbra@efficios.com>

On 2019-12-17 9:39 a.m., Mathieu Desnoyers wrote:
> I was expecting review from Geneviève and Julien on this patch, but
> never heard back from
> them.
> 
> Geneviève, Julien, Michael, can you review this patch please ?
> 
> Thanks,
> 
> Mathieu

It builds on all the latest tags of the stable kernel branches we
support and the patch itself looks good to me but Geneviève's or
Julien's feedback would be appreciated.

Michael
_______________________________________________
lttng-dev mailing list
lttng-dev@lists.lttng.org
https://lists.lttng.org/cgi-bin/mailman/listinfo/lttng-dev

  parent reply	other threads:[~2019-12-17 17:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20191113163814.31606-1-walbroel@silexica.com>
2019-12-17  8:56 ` Fwd: [PATCH lttng-modules] Add UDP and ICMP packet header information to the tracepoint: Florian Walbroel
     [not found] ` <7b697030-2d01-90bf-0225-fe52b42e9cd0@silexica.com>
2019-12-17 14:39   ` Mathieu Desnoyers
     [not found]   ` <1666401048.8323.1576593591017.JavaMail.zimbra@efficios.com>
2019-12-17 17:20     ` Michael Jeanson [this message]
     [not found]     ` <88c1b057-e920-433e-77b0-03dd04cd14de@efficios.com>
2020-03-09 10:55       ` Florian Walbroel
2020-03-09 15:28 ` 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='88c1b057-e920-433e-77b0-03dd04cd14de__35412.5898958714$1576603271$gmane$org@efficios.com' \
    --to=mjeanson@efficios.com \
    --cc=ju@klipix.org \
    --cc=lttng-dev@lists.lttng.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=walbroel@silexica.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).