linux-trace-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tomas Glozar <tglozar@redhat.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Linux Trace Kernel <linux-trace-kernel@vger.kernel.org>,
	John Kacur <jkacur@redhat.com>,
	Luis Goncalves <lgoncalv@redhat.com>,
	Costa Shulyupin <costa.shul@redhat.com>,
	Crystal Wood <crwood@redhat.com>,
	Wander Lairson Costa <wander@redhat.com>
Subject: Re: [PATCH v2 1/3] tools/rtla: Fix --on-threshold always triggering
Date: Fri, 17 Oct 2025 05:11:46 -0400	[thread overview]
Message-ID: <20251017051146.5f6a8901@batman.local.home> (raw)
In-Reply-To: <CAP4=nvSmJOdoO8q125sdzvR7ix1oVsNobSRtWb7ADUADdzEPiw@mail.gmail.com>

On Fri, 17 Oct 2025 09:38:04 +0200
Tomas Glozar <tglozar@redhat.com> wrote:
> 
> It seems that this patchset containing fixes for recently merged RTLA
> code consolidation [1] has no further comments. Could you take it?
> (Unless you have any comments, of course.)
> 
> [1] https://lore.kernel.org/linux-trace-kernel/20250907022325.243930-1-crwood@redhat.com/T/

I'll take a look at it next week. I added it to my "delegate" in Patchwork:

  https://patchwork.kernel.org/project/linux-trace-kernel/list/?series=1008975

So hopefully, I don't forget.

We need to start making you the maintainer too ;-)

-- Steve

  reply	other threads:[~2025-10-17  9:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07  9:53 [PATCH v2 1/3] tools/rtla: Fix --on-threshold always triggering Tomas Glozar
2025-10-07  9:53 ` [PATCH v2 2/3] rtla/tests: Extend action tests to 5s Tomas Glozar
2025-10-17 12:34   ` Wander Lairson Costa
2025-10-07  9:53 ` [PATCH v2 3/3] rtla/tests: Fix osnoise test calling timerlat Tomas Glozar
2025-10-17 12:21   ` Wander Lairson Costa
2025-10-17  7:38 ` [PATCH v2 1/3] tools/rtla: Fix --on-threshold always triggering Tomas Glozar
2025-10-17  9:11   ` Steven Rostedt [this message]
2025-10-17 12:21 ` Wander Lairson Costa

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=20251017051146.5f6a8901@batman.local.home \
    --to=rostedt@goodmis.org \
    --cc=costa.shul@redhat.com \
    --cc=crwood@redhat.com \
    --cc=jkacur@redhat.com \
    --cc=lgoncalv@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-trace-kernel@vger.kernel.org \
    --cc=tglozar@redhat.com \
    --cc=wander@redhat.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).