public inbox for linux-trace-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Rostedt <rostedt@goodmis.org>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Crystal Wood <crwood@redhat.com>,
	linux-trace-kernel@vger.kernel.org,
	John Kacur <jkacur@redhat.com>,
	Costa Shulyupin <costa.shul@redhat.com>
Subject: Re: [PATCH v2 0/7] tools/rtla: Code consolidation and osnoise actions
Date: Sat, 27 Sep 2025 04:44:54 -0400	[thread overview]
Message-ID: <20250927044454.0525d39c@batman.local.home> (raw)
In-Reply-To: <CAP4=nvQR3YDNVhka9QCNQVB=QEytxLPdFrx_nNJbNm7-r9ujDg@mail.gmail.com>

On Fri, 26 Sep 2025 16:19:28 +0200
Tomas Glozar <tglozar@redhat.com> wrote:

> Can you take this patchset? (As a major change, this should go to
> linux-next first I guess, not sure if the timing is right for that, my
> knowledge on upstream kernel workflow is still a bit flaky).

Normally, new code now would be a bit late for the merge window, but
code in the tools directory isn't as strict. Thus, this is fine to push
for the next merge window. I'll pull it in and send it to linux-next.


> 
> I reviewed it already, but it seems that patchwork doesn't understand
> Reviewed-by on a cover letter (even though b4 understands it). I did
> Reviewed-by on the original patches where I didn't request any
> changes, but v2 did not preserve that, so I put it on the cover
> letter.

I'll add the Reviewed by manually if need be.

Thanks,

-- Steve

  reply	other threads:[~2025-09-27  9:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-07  2:23 [PATCH v2 0/7] tools/rtla: Code consolidation and osnoise actions Crystal Wood
2025-09-07  2:23 ` [PATCH v2 1/7] tools/rtla: Consolidate common parameters into shared structure Crystal Wood
2025-09-07  2:23 ` [PATCH v2 2/7] tools/rtla: Move top/hist params into common struct Crystal Wood
2025-09-07  2:23 ` [PATCH v2 3/7] tools/rtla: Create common_apply_config() Crystal Wood
2025-09-07  2:23 ` [PATCH v2 4/7] tools/rtla: Consolidate code between osnoise/timerlat and hist/top Crystal Wood
2025-09-07 19:51   ` Costa Shulyupin
2025-09-08 13:53     ` Costa Shulyupin
2025-09-07  2:23 ` [PATCH v2 5/7] tools/rtla: Fix -A option name in test comment Crystal Wood
2025-09-07  2:23 ` [PATCH v2 6/7] tools/rtla: Add test engine support for unexpected output Crystal Wood
2025-09-08 14:48   ` Crystal Wood
2025-09-07  2:23 ` [PATCH v2 7/7] tools/rtla: Add remaining support for osnoise actions Crystal Wood
2025-09-09 11:25 ` [PATCH v2 0/7] tools/rtla: Code consolidation and " Tomas Glozar
2025-09-26 14:19 ` Tomas Glozar
2025-09-27  8:44   ` Steven Rostedt [this message]
2025-09-27  9:47     ` Steven Rostedt
2025-09-27 10:09       ` Steven Rostedt

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