From: John Kacur <jkacur@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>,
Daniel Bristot de Oliveria <bristot@redhat.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
linux-trace-devel@vger.kernel.org, John Kacur <jkacur@redhat.com>
Subject: [PATCH 2/2] rtla: Minor fix to grammar in README.txt
Date: Sat, 2 Apr 2022 00:39:39 -0400 [thread overview]
Message-ID: <20220402043939.6962-2-jkacur@redhat.com> (raw)
In-Reply-To: <20220402043939.6962-1-jkacur@redhat.com>
"The rtla" doesn't make sense, change it to "The rtla tool"
This is better than removing the word "The" since some packaging tools
need the description to start with a capital letter.
Signed-off-by: John Kacur <jkacur@redhat.com>
---
tools/tracing/rtla/README.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/tools/tracing/rtla/README.txt b/tools/tracing/rtla/README.txt
index 6c88446f7e74..3b809eeff5f9 100644
--- a/tools/tracing/rtla/README.txt
+++ b/tools/tracing/rtla/README.txt
@@ -1,6 +1,6 @@
RTLA: Real-Time Linux Analysis tools
-The rtla is a meta-tool that includes a set of commands that
+The rtla tool is a meta-tool that includes a set of commands that
aims to analyze the real-time properties of Linux. But, instead of
testing Linux as a black box, rtla leverages kernel tracing
capabilities to provide precise information about the properties
--
2.31.1
next prev parent reply other threads:[~2022-04-02 4:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-02 4:39 [PATCH 1/2] rtla: Don't overwrite existing directory mode John Kacur
2022-04-02 4:39 ` John Kacur [this message]
2022-04-08 13:10 ` [PATCH 2/2] rtla: Minor fix to grammar in README.txt Daniel Bristot de Oliveira
2022-04-08 13:49 ` John Kacur
2022-04-08 14:11 ` Daniel Bristot de Oliveira
2022-04-08 13:11 ` [PATCH 1/2] rtla: Don't overwrite existing directory mode Daniel Bristot de Oliveira
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=20220402043939.6962-2-jkacur@redhat.com \
--to=jkacur@redhat.com \
--cc=bristot@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=linux-trace-devel@vger.kernel.org \
--cc=rostedt@goodmis.org \
/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.