From: John Kacur <jkacur@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>
Cc: linux-trace-kernel@vger.kernel.org,
Steven Rostedt <rostedt@goodmis.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] rtla: Fix parsing of multi-character short options
Date: Tue, 2 Jun 2026 12:21:49 -0400 [thread overview]
Message-ID: <20260602162150.75782-1-jkacur@redhat.com> (raw)
In-Reply-To: <20260602125506.3325345-1-tglozar@redhat.com>
On Tue, 2 Jun 2026 14:55:06 +0200, Tomas Glozar wrote:
> rtla: Fix parsing of multi-character short options
Thanks for the fix! I've tested this patch with a comprehensive test suite
covering all rtla commands (timerlat hist/top, osnoise hist/top, hwnoise)
with the four option formats:
-p 100 (short with space)
-p100 (short attached - previously broken)
--period=100 (long with equals)
--period 100 (long with space)
All 20 tests pass. The fix correctly resolves the issue where -p100 was
being parsed as multiple separate options.
Tested-by: John Kacur <jkacur@redhat.com>
prev parent reply other threads:[~2026-06-02 16:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-02 12:55 [PATCH] rtla: Fix parsing of multi-character short options Tomas Glozar
2026-06-02 12:56 ` Tomas Glozar
2026-06-02 16:21 ` John Kacur [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=20260602162150.75782-1-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=rostedt@goodmis.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