From: Steven Rostedt <rostedt@goodmis.org>
To: Gabriele Monaco <gmonaco@redhat.com>
Cc: linux-kernel@vger.kernel.org, Nam Cao <namcao@linutronix.de>,
Tomas Glozar <tglozar@redhat.com>, Juri Lelli <jlelli@redhat.com>,
Clark Williams <williams@redhat.com>,
John Kacur <jkacur@redhat.com>
Subject: Re: [PATCH 0/5] tools/verification: Improvements to rv and rvgen
Date: Tue, 29 Jul 2025 13:12:15 -0400 [thread overview]
Message-ID: <20250729131215.20fa9bf2@batman.local.home> (raw)
In-Reply-To: <735d8530-f733-4973-8b0d-ac601d0a1799@redhat.com>
On Thu, 24 Jul 2025 18:07:35 +0000 (UTC)
Gabriele Monaco <gmonaco@redhat.com> wrote:
> Alright, but I guess going forward I'll try to keep changes separated anyway, if possible.
>
> Right, 4 is problematic here, it should apply cleanly on next though, maybe I should have rebased on your tree instead..
>
> So do I submit together 4,5 and the kernel ones? Or again all together?
If you haven't noticed, I already just took it ;-)
-- Steve
next prev parent reply other threads:[~2025-07-29 17:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-23 16:12 [PATCH 0/5] tools/verification: Improvements to rv and rvgen Gabriele Monaco
2025-07-23 16:12 ` [PATCH 1/5] tools/rv: Do not skip idle in trace Gabriele Monaco
2025-07-23 16:12 ` [PATCH 2/5] tools/rv: Stop gracefully also on SIGTERM Gabriele Monaco
2025-07-23 16:12 ` [PATCH 3/5] tools/dot2c: Fix generated files going over 100 column limit Gabriele Monaco
2025-07-23 16:12 ` [PATCH 4/5] verification/rvgen: Organise Kconfig entries for nested monitors Gabriele Monaco
2025-07-23 16:12 ` [PATCH 5/5] rv: Return init error when registering monitors Gabriele Monaco
2025-07-24 14:40 ` [PATCH 0/5] tools/verification: Improvements to rv and rvgen Steven Rostedt
2025-07-24 18:07 ` Gabriele Monaco
2025-07-29 17:12 ` Steven Rostedt [this message]
2025-07-29 21:18 ` Steven Rostedt
2025-07-30 6:06 ` Gabriele Monaco
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=20250729131215.20fa9bf2@batman.local.home \
--to=rostedt@goodmis.org \
--cc=gmonaco@redhat.com \
--cc=jkacur@redhat.com \
--cc=jlelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namcao@linutronix.de \
--cc=tglozar@redhat.com \
--cc=williams@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 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.