From: John Kacur <jkacur@redhat.com>
To: Tomas Glozar <tglozar@redhat.com>
Cc: Clark Williams <williams@redhat.com>,
Linux RT Users <linux-rt-users@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] rteval: Introduce E2E tests with output checking
Date: Mon, 10 Nov 2025 14:07:33 -0500 (EST) [thread overview]
Message-ID: <e24beb3c-e511-aa59-7986-38dd44a06180@redhat.com> (raw)
In-Reply-To: <20251107134749.257350-1-tglozar@redhat.com>
8<
Signed-off-by: John Kacur <jkacur@redhat.com>
prev parent reply other threads:[~2025-11-10 19:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-07 13:47 [PATCH v2 1/3] rteval: Introduce E2E tests with output checking Tomas Glozar
2025-11-07 13:47 ` [PATCH v2 2/3] rteval: Move unittest.py to tests/ Tomas Glozar
2025-11-10 19:11 ` John Kacur
2025-11-11 7:52 ` Tomas Glozar
2025-11-07 13:47 ` [PATCH v2 3/3] rteval: Add README-tests Tomas Glozar
2025-11-10 19:12 ` John Kacur
2025-11-11 7:53 ` Tomas Glozar
2025-11-10 19:07 ` 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=e24beb3c-e511-aa59-7986-38dd44a06180@redhat.com \
--to=jkacur@redhat.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=tglozar@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