From: Steven Rostedt <rostedt@goodmis.org>
To: Pierre Gondois <pierre.gondois@arm.com>
Cc: Linux Trace Devel <linux-trace-devel@vger.kernel.org>
Subject: Re: [PATCH 2/5] trace-cmd: usage: Update usage for trace-cmd split
Date: Fri, 19 Jan 2024 12:31:15 -0500 [thread overview]
Message-ID: <20240119123115.7494bf1e@gandalf.local.home> (raw)
In-Reply-To: <efb02cc0-65d9-4b76-9ec6-030a6f39b1c5@arm.com>
On Mon, 15 Jan 2024 18:22:15 +0100
Pierre Gondois <pierre.gondois@arm.com> wrote:
> > The above looks like it has nothing to do with the usage, and was perhaps
> > accidentally merged in this patch?
>
> Yes right,
> something wrong happened while rebasing, sorry for that...
Ah can you send a v2 on this patch series.
For the fixes I can pull them immediately. The updates to the split
functionality can come in a separate patch set.
-- Steve
next prev parent reply other threads:[~2024-01-19 17:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-12 8:39 [PATCH 0/5] trace-cmd: split: Handle splitting files with multiple instances Pierre Gondois
2024-01-12 8:39 ` [PATCH 1/5] trace-cmd: split: Small fixes Pierre Gondois
2024-01-12 8:39 ` [PATCH 2/5] trace-cmd: usage: Update usage for trace-cmd split Pierre Gondois
2024-01-12 15:37 ` Steven Rostedt
2024-01-15 17:22 ` Pierre Gondois
2024-01-19 17:31 ` Steven Rostedt [this message]
2024-01-12 8:39 ` [PATCH 3/5] trace-cmd: split: Store instances in local list Pierre Gondois
2024-01-12 8:39 ` [PATCH 4/5] trace-cmd: split: Add functions to generate temp files Pierre Gondois
2024-01-12 8:39 ` [PATCH 5/5] trace-cmd: split: Handle splitting files with multiple instances Pierre Gondois
2024-01-12 16:18 ` Steven Rostedt
2024-01-15 17:25 ` Pierre Gondois
2024-01-15 18:56 ` Steven Rostedt
2024-01-19 16:41 ` Pierre Gondois
2024-01-19 17:06 ` Pierre Gondois
2024-01-19 17:25 ` Steven Rostedt
2024-01-12 15:36 ` [PATCH 0/5] " 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=20240119123115.7494bf1e@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=pierre.gondois@arm.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 read-only IMAP folder(s) and NNTP newsgroup(s).