From: Steven Rostedt <rostedt@goodmis.org>
To: Costa Shulyupin <costa.shul@redhat.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
linux-trace-kernel@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org, Tomas Glozar <tglozar@redhat.com>
Subject: Re: [PATCH] Documentation/rtla: Describe exit status
Date: Tue, 1 Jul 2025 17:44:15 -0400 [thread overview]
Message-ID: <20250701174415.69edef99@batman.local.home> (raw)
In-Reply-To: <20250608105531.758809-2-costa.shul@redhat.com>
On Sun, 8 Jun 2025 13:55:30 +0300
Costa Shulyupin <costa.shul@redhat.com> wrote:
> Commit 18682166f61494072d58 ("rtla: Set distinctive exit value for failed
> tests") expands exit status making it useful.
>
> Add section 'EXIT STATUS' and required SPDX-License-Identifier
> to the documentation.
>
> Signed-off-by: Costa Shulyupin <costa.shul@redhat.com>
Acked-by: Steven Rostedt (Google) <rostedt@goodmis.org>
-- Steve
> ---
> Documentation/tools/rtla/common_appendix.rst | 10 ++++++++++
> 1 file changed, 10 insertions(+)
>
> diff --git a/Documentation/tools/rtla/common_appendix.rst b/Documentation/tools/rtla/common_appendix.rst
> index b5cf2dc223df..a6233ca8e6d6 100644
> --- a/Documentation/tools/rtla/common_appendix.rst
> +++ b/Documentation/tools/rtla/common_appendix.rst
> @@ -1,3 +1,13 @@
> +.. SPDX-License-Identifier: GPL-2.0
> +EXIT STATUS
> +===========
> +
> +::
> +
> + 0 Passed: the test did not hit the stop tracing condition
> + 1 Error: invalid argument
> + 2 Failed: the test hit the stop tracing condition
> +
> REPORTING BUGS
> ==============
> Report bugs to <linux-kernel@vger.kernel.org>
next prev parent reply other threads:[~2025-07-01 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-08 10:55 [PATCH] Documentation/rtla: Describe exit status Costa Shulyupin
2025-07-01 21:44 ` Steven Rostedt [this message]
2025-07-17 20:26 ` Jonathan Corbet
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=20250701174415.69edef99@batman.local.home \
--to=rostedt@goodmis.org \
--cc=corbet@lwn.net \
--cc=costa.shul@redhat.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--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 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.