From: Petr Vorel <pvorel@suse.cz>
To: Li Wang <liwang@redhat.com>
Cc: Jan Hoeppner <hoeppner@linux.vnet.ibm.com>,
Elif Aslan <elas@linux.vnet.ibm.com>,
ltp@lists.linux.it
Subject: Re: [LTP] [PATCH 1/1] Remove s390x test
Date: Thu, 9 Apr 2026 08:13:47 +0200 [thread overview]
Message-ID: <20260409061347.GA64002@pevik> (raw)
In-Reply-To: <ac8f0MPErGdZzDNe@redhat.com>
Hi Li,
> On Thu, Apr 02, 2026 at 10:04:31PM +0200, Petr Vorel wrote:
> > vmcp_m.sh is a pure user space test (out of LTP scope). While test
> > claims testing vmcp tool and module IMHO it's mainly testing vmcp basic
> > usage (-h, -v), exit codes on error. The only real use is 'vmcp q dasd'.
> > s390-tools maintainers confirmed they have internal CI and are working
> > on to be part of s390-tools on GitHub [1]. Another reason to remove.
> > Remove also runtest/s390x_tests, which contained only this test.
> Agreed.
> Reviewed-by: Li Wang <liwang@redhat.com>
Thanks for your ack, merged!
Kind regards,
Petr
--
Mailing list info: https://lists.linux.it/listinfo/ltp
prev parent reply other threads:[~2026-04-09 6:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-02 20:04 [LTP] [PATCH 1/1] Remove s390x test Petr Vorel
2026-04-03 2:02 ` Li Wang via ltp
2026-04-09 6:13 ` Petr Vorel [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=20260409061347.GA64002@pevik \
--to=pvorel@suse.cz \
--cc=elas@linux.vnet.ibm.com \
--cc=hoeppner@linux.vnet.ibm.com \
--cc=liwang@redhat.com \
--cc=ltp@lists.linux.it \
/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