From: John Kacur <jkacur@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] rteval: Correct Python version in doc/rteval.txt
Date: Tue, 8 Aug 2023 14:29:57 -0400 (EDT) [thread overview]
Message-ID: <d98aab0-3f8b-ec8e-e8b1-b9c7dc47852@redhat.com> (raw)
In-Reply-To: <20230808115201.43187-1-tglozar@redhat.com>
On Tue, 8 Aug 2023, Tomas Glozar wrote:
> doc/rteval.txt specifies that rteval is a Python 2.x program. This is
> not true, since rteval no longer works with Python 2.x:
> $ python2 rteval-cmd
> File "rteval-cmd", line 67
> print(f"Don't know how to summarize {repfile} (tarfile open failed)")
> ^
> SyntaxError: invalid syntax
>
> Replace "Python 2.x" with "Python 3.x".
>
> Signed-off-by: Tomas Glozar <tglozar@redhat.com>
> ---
> doc/rteval.txt | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/doc/rteval.txt b/doc/rteval.txt
> index 7342866..569168e 100644
> --- a/doc/rteval.txt
> +++ b/doc/rteval.txt
> @@ -21,7 +21,7 @@ of a network packet). To give a realtime application the best chance
> of meeting its deadline(s), a realtime OS must minimize the time
> between event occurance and the servicing of that event (latency).
>
> -This paper describes the 'rteval' program, a Python 2.x program
> +This paper describes the 'rteval' program, a Python 3.x program
> developed at Red Hat to help quantify realtime performance on the
> Realtime kernel. Rteval is an attempt to put together a synthetic
> benchmark which mimics a well behaved realtime application, running on
> --
> 2.39.3
>
>
Thanks for the clean-up
Signed-off-by: John Kacur <jkacur@redhat.com>
prev parent reply other threads:[~2023-08-08 20:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-08 11:52 [PATCH] rteval: Correct Python version in doc/rteval.txt Tomas Glozar
2023-08-08 18:29 ` 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=d98aab0-3f8b-ec8e-e8b1-b9c7dc47852@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-rt-users@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;
as well as URLs for NNTP newsgroup(s).