From: John Kacur <jkacur@redhat.com>
To: Anubhav Shelat <ashelat@redhat.com>
Cc: linux-rt-users@vger.kernel.org, kcarcia@redhat.com
Subject: Re: [PATCH] cyclicdeadline: removed unnesessary text in usage message
Date: Tue, 8 Aug 2023 14:58:34 -0400 (EDT) [thread overview]
Message-ID: <30b8b1e0-f73c-cd85-257e-3eec5a86f5ad@redhat.com> (raw)
In-Reply-To: <20230728152955.48977-1-ashelat@redhat.com>
On Fri, 28 Jul 2023, Anubhav Shelat wrote:
> removed unnesessary text in usage message
> Signed-off-by: Anubhav Shelat <ashelat@redhat.com>
> ---
> src/sched_deadline/cyclicdeadline.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/src/sched_deadline/cyclicdeadline.c b/src/sched_deadline/cyclicdeadline.c
> index fbe3a75c60b8..4b4050fcbbb7 100644
> --- a/src/sched_deadline/cyclicdeadline.c
> +++ b/src/sched_deadline/cyclicdeadline.c
> @@ -685,7 +685,6 @@ static void usage(int error)
> "-a [CPUSET] --affinity Comma/hyphen separated list of CPUs to run deadline\n"
> " tasks on. An empty CPUSET runs on all CPUs a deadline\n"
> " task.\n"
> - " on CPU 4, and thread #5 on CPU 5.\n"
> "-D TIME --duration Specify a length for the test run.\n"
> " Append 'm', 'h', or 'd' to specify minutes, hours or\n"
> " days\n"
> @@ -1234,7 +1233,7 @@ int main(int argc, char **argv)
> percent = nr_cpus * 80 / nr_threads;
> }
>
> - /* Set up the data while sill in SCHED_FIFO */
> + /* Set up the data while still in SCHED_FIFO */
> for (i = 0; i < nr_threads; i++) {
> sd = &sched_data[i];
> /*
> --
> 2.39.3
>
>
Signed-off-by: John Kacur <jkacur@redhat.com>
prev parent reply other threads:[~2023-08-08 19:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 15:29 [PATCH] cyclicdeadline: removed unnesessary text in usage message Anubhav Shelat
2023-08-08 18:58 ` 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=30b8b1e0-f73c-cd85-257e-3eec5a86f5ad@redhat.com \
--to=jkacur@redhat.com \
--cc=ashelat@redhat.com \
--cc=kcarcia@redhat.com \
--cc=linux-rt-users@vger.kernel.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 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).