linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <dwagner@suse.de>
To: Clark Williams <williams@redhat.com>, John Kacur <jkacur@redhat.com>
Cc: linux-rt-users@vger.kernel.org, Daniel Wagner <dwagner@suse.de>
Subject: [rt-tests 0/4] Streamlining code base?
Date: Wed,  2 Sep 2020 10:27:21 +0200	[thread overview]
Message-ID: <20200902082725.20037-1-dwagner@suse.de> (raw)

Hi Clark and John,

I'd like to streamline all tools, so that the usage, command arguments
and the output is more consistent. Every tool seems to be a bit
different which makes all automatization around the tools more complex
than needed.

Eventually, I'd like to add an easy machine parseable output from all
tools. So what do you think? Stupid effort, go away?

Here are a bunch of patches to illustrate what I mean. Before invest
too much time I'd like to discuss it, e.g. format.

Cheers,
Daniel

Daniel Wagner (4):
  cyclicdeadline: Streamline usage output and man page
  deadline_test: Streamline usage output and man page
  oslat: Streamline usage output and man page
  oslat: Use string parser utilies

 src/include/rt-utils.h              |   1 +
 src/lib/rt-utils.c                  |  30 ++++++
 src/oslat/oslat.8                   |   2 +-
 src/oslat/oslat.c                   | 143 ++++++++--------------------
 src/sched_deadline/cyclicdeadline.8 |  24 ++---
 src/sched_deadline/cyclicdeadline.c |  41 ++++----
 src/sched_deadline/deadline_test.8  |  37 ++++---
 src/sched_deadline/deadline_test.c  |  47 +++++----
 8 files changed, 145 insertions(+), 180 deletions(-)

-- 
2.28.0


             reply	other threads:[~2020-09-02  8:27 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-02  8:27 Daniel Wagner [this message]
2020-09-02  8:27 ` [rt-tests 1/4] cyclicdeadline: Streamline usage output and man page Daniel Wagner
2020-09-02  8:27 ` [rt-tests 2/4] deadline_test: " Daniel Wagner
2020-09-02  8:27 ` [rt-tests 3/4] oslat: " Daniel Wagner
2020-09-02  8:27 ` [rt-tests 4/4] oslat: Use string parser utilies Daniel Wagner
2020-09-04  1:39 ` [rt-tests 0/4] Streamlining code base? Clark Williams
2020-09-04  6:31   ` Daniel Wagner
2020-09-04 15:40     ` John Kacur
2020-09-07  8:13       ` Daniel Wagner
2020-09-08 15:23         ` John Kacur

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=20200902082725.20037-1-dwagner@suse.de \
    --to=dwagner@suse.de \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=williams@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).