linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Daniel Wagner <dwagner@suse.de>
To: John Kacur <jkacur@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
	linux-rt-users@vger.kernel.org, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH rt-tests 1/2] oslat: Print version string
Date: Wed, 10 Feb 2021 19:21:14 +0100	[thread overview]
Message-ID: <20210210182114.xbxw62gj6n6ox6pt@beryllium.lan> (raw)
In-Reply-To: <7a61c0fd-90fe-69a4-5d26-4b688e2147b5@redhat.com>

On Wed, Feb 10, 2021 at 12:59:29PM -0500, John Kacur wrote:
> Are you really telling me you won't fix a problem you introduced unless
> I first take all the other code you would like to get in rt-tests?

I've already done the long option support in the JSON series. It would
make my life way simpler if those bits would be in the tree.

I think, the simplest fix for now is to temporarily a local fix for
oslat.

  reply	other threads:[~2021-02-10 18:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10 16:54 [PATCH rt-tests 0/2] oslat fixes Daniel Wagner
2021-02-10 16:54 ` [PATCH rt-tests 1/2] oslat: Print version string Daniel Wagner
2021-02-10 17:12   ` Peter Xu
2021-02-10 17:28   ` John Kacur
2021-02-10 17:33     ` Daniel Wagner
2021-02-10 17:53       ` Peter Xu
2021-02-10 18:15         ` Daniel Wagner
2021-02-10 19:26           ` Peter Xu
2021-02-10 17:59       ` John Kacur
2021-02-10 18:21         ` Daniel Wagner [this message]
2021-02-10 19:12           ` John Kacur
2021-02-11  4:32             ` John Kacur
2021-02-10 16:54 ` [PATCH rt-tests 2/2] oslat: Use cpuset size as upper bound Daniel Wagner
2021-02-10 17:14   ` Peter Xu
2021-02-11  4:28   ` John Kacur
2021-02-11 15:24     ` Peter Xu

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=20210210182114.xbxw62gj6n6ox6pt@beryllium.lan \
    --to=dwagner@suse.de \
    --cc=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=peterx@redhat.com \
    --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).