Linux Trace Development
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Benjamin Drung <benjamin.drung@canonical.com>
Cc: linux-trace-devel@vger.kernel.org
Subject: Re: [PATCH v2 0/3] Ubuntu patches
Date: Thu, 24 Sep 2026 15:45:34 -0400	[thread overview]
Message-ID: <20260924154534.318f6ec2@fedora> (raw)
In-Reply-To: <20260923205650.2638166-1-benjamin.drung@canonical.com>


Thanks,

I'm actually in the middle of traveling until Oct 10th and will likely
not be able to look at these until then.I'm hoping to triage the bugs
and changes sent to the trace-cmd and library code in October.

-- Steve


On Wed, 23 Sep 2026 22:56:29 +0200
Benjamin Drung <benjamin.drung@canonical.com> wrote:

> Hi,
> 
> with quite some delay, here are the requested changes.
> 
> v2:
>  - Added missing Signed-off-by tags.
> 
> Adrien Nader (1):
>   libtracefs utest: Only use online CPUs during tests
> 
> Benjamin Drung (2):
>   libtracefs: Use LIBTRACEFS_STATIC for utest
>   libtracefs: Support EXTRA_LIBS for utest
> 
>  utest/Makefile        |  7 +++++--
>  utest/tracefs-utest.c | 10 +++++-----
>  2 files changed, 10 insertions(+), 7 deletions(-)
> 


      parent reply	other threads:[~2026-09-24 19:52 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-05 14:53 [PATCH 1/2] libtracefs: Use LIBTRACEFS_STATIC for utest Benjamin Drung
2026-06-05 14:53 ` [PATCH 2/2] libtracefs: Support EXTRA_LIBS " Benjamin Drung
2026-08-26 20:37 ` [PATCH 1/2] libtracefs: Use LIBTRACEFS_STATIC " Steven Rostedt
2026-09-23 20:56   ` [PATCH v2 0/3] Ubuntu patches Benjamin Drung
2026-09-23 20:56     ` [PATCH v2 1/3] libtracefs utest: Only use online CPUs during tests Benjamin Drung
2026-09-23 20:56     ` [PATCH v2 2/3] libtracefs: Use LIBTRACEFS_STATIC for utest Benjamin Drung
2026-09-23 20:56     ` [PATCH v2 3/3] libtracefs: Support EXTRA_LIBS " Benjamin Drung
2026-09-24 19:45     ` Steven Rostedt [this message]

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=20260924154534.318f6ec2@fedora \
    --to=rostedt@goodmis.org \
    --cc=benjamin.drung@canonical.com \
    --cc=linux-trace-devel@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