linux-rt-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: John Kacur <jkacur@redhat.com>
To: Sana Sharma <sansshar@redhat.com>
Cc: linux-rt-users@vger.kernel.org
Subject: Re: [PATCH v1] rteval: Edited documentation for multistressor support
Date: Tue,  3 Nov 2026 12:55:17 -0500	[thread overview]
Message-ID: <20261103175517.107723-3-jkacur@redhat.com> (raw)
In-Reply-To: <auSkiUhcFJAO2-_Y@fedora>

On Fri, 30 Oct 2026 at 10:07:05 -0400, Sana Sharma wrote:
> [PATCH v1] rteval: Edited documentation for multistressor support

Looks good - thanks for dropping the stale --stressng-option /
--stressng-arg entries and documenting the new flags. The content matches
the actual behaviour (workers default 0 = one per CPU).

Two tiny fixes for a v2:
 - the commit message says "docs/rteval.8"; the path is "doc/rteval.8".
 - typo: "specfically" -> "specifically".

John

      reply	other threads:[~2026-11-03 17:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-30 14:07 [PATCH v1] rteval: Edited documentation for multistressor support Sana Sharma
2026-11-03 17:55 ` 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=20261103175517.107723-3-jkacur@redhat.com \
    --to=jkacur@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=sansshar@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).