From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 0/8] network/nfs: fix/cleanup tests
Date: Thu, 4 Aug 2016 13:13:51 +0300 [thread overview]
Message-ID: <57A3155F.9030804@oracle.com> (raw)
In-Reply-To: <1466432936-3099-1-git-send-email-alexey.kodanev@oracle.com>
Hi,
On 06/20/2016 05:28 PM, Alexey Kodanev wrote:
> Alexey Kodanev (8):
> lib: add safe_gethostname()
> network/nfs05: rewrite the test, make use of new library
> network/nfs_lib.sh: add options, socket type and NFS ver
> network/nfs/fsx: cleanup test, use test_net library
> network/nfs/nfsstat: cleanup test, use test_net.sh library
> network/nfs/nfsflock: clenaup & use test_net library
> network/nfs/nfs_fsstress: remove fsstress test
> network/nfs: remove README
Patch-set applied except first two patches that were sent separately as v2.
Thanks,
Alexey
prev parent reply other threads:[~2016-08-04 10:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 14:28 [LTP] [PATCH 0/8] network/nfs: fix/cleanup tests Alexey Kodanev
2016-06-20 14:28 ` [LTP] [PATCH resend 1/8] lib: add safe_gethostname() Alexey Kodanev
2016-06-20 14:28 ` [LTP] [PATCH resend 2/8] network/nfs05: rewrite the test, make use of new library Alexey Kodanev
2016-06-20 14:28 ` [LTP] [PATCH 3/8] network/nfs_lib.sh: add options, socket type and NFS ver Alexey Kodanev
2016-06-20 14:28 ` [LTP] [PATCH 4/8] network/nfs/fsx: cleanup test, use test_net library Alexey Kodanev
2016-06-20 14:28 ` [LTP] [PATCH 5/8] network/nfs/nfsstat: cleanup test, use test_net.sh library Alexey Kodanev
2016-06-20 14:28 ` [LTP] [PATCH 6/8] network/nfs/nfsflock: clenaup & use test_net library Alexey Kodanev
2016-06-20 14:28 ` [LTP] [PATCH 7/8] network/nfs/nfs_fsstress: remove fsstress test Alexey Kodanev
2016-06-20 14:28 ` [LTP] [PATCH 8/8] network/nfs: remove README Alexey Kodanev
2016-08-04 10:13 ` Alexey Kodanev [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=57A3155F.9030804@oracle.com \
--to=alexey.kodanev@oracle.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