From: Jes.Sorensen@redhat.com
To: neilb@suse.de
Cc: linux-raid@vger.kernel.org
Subject: [PATCH 0/2] Test suite enhancements
Date: Tue, 22 May 2012 18:55:28 +0200 [thread overview]
Message-ID: <1337705730-7335-1-git-send-email-Jes.Sorensen@redhat.com> (raw)
From: Jes Sorensen <Jes.Sorensen@redhat.com>
Hi,
Two fixes for the testsuite. The first is just to allow it to run on
systems which do not include the multipath module. The second adds
command line arguments to 'test'. In particular it makes it possible
to specify explicit tests to run. I believe I managed to preserve the
behavior for old style arguments.
Cheers,
Jes
Jes Sorensen (2):
Check for multipath module before running multipath tests
Add command line argument parsing to 'test' sript
test | 94 ++++++++++++++++++++++++++++++++++++++++-------------
tests/00multipath | 5 +++
2 files changed, 76 insertions(+), 23 deletions(-)
--
1.7.7.6
next reply other threads:[~2012-05-22 16:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 16:55 Jes.Sorensen [this message]
2012-05-22 16:55 ` [PATCH 1/2] Check for multipath module before running multipath tests Jes.Sorensen
2012-05-22 16:55 ` [PATCH 2/2] Add command line argument parsing to 'test' sript Jes.Sorensen
2012-05-23 3:39 ` NeilBrown
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=1337705730-7335-1-git-send-email-Jes.Sorensen@redhat.com \
--to=jes.sorensen@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).