From: John Kacur <jkacur@redhat.com>
To: Daniel Wagner <dwagner@suse.de>
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 23:32:52 -0500 (EST) [thread overview]
Message-ID: <cc83af39-8d37-4ece-d04c-77a415f705@redhat.com> (raw)
In-Reply-To: <eaf911f6-1e4b-ce13-7b26-45b01854f7e7@redhat.com>
On Wed, 10 Feb 2021, John Kacur wrote:
>
>
> On Wed, 10 Feb 2021, Daniel Wagner wrote:
>
> > 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.
> >
>
> Just add a fix onto for the oslat problem on the end of your series
> I'll be done the review soon.
>
> If we need to do any backporting then we'll do that.
>
> Cheers, Thanks
>
> John
>
I rewound your patches in git, and applied the two oslat fixes and
reapplied your patches with a git interactive rebase, and then I pushed
them for others to try before I'm ready to push them upstream
Anyone who wants to try the new json stuff it's in a branch called
unstable/devel/rt-numa-json
The numa changes need more testing before integrate them, but
this should make it easier for others to try it out.
John
next prev parent reply other threads:[~2021-02-11 4:33 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
2021-02-10 19:12 ` John Kacur
2021-02-11 4:32 ` John Kacur [this message]
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=cc83af39-8d37-4ece-d04c-77a415f705@redhat.com \
--to=jkacur@redhat.com \
--cc=dwagner@suse.de \
--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