From: Alexey Kodanev <alexey.kodanev@oracle.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 02/10] network/nfs: rename nfs dir to nfs_stress
Date: Tue, 06 Oct 2015 16:44:24 +0300 [thread overview]
Message-ID: <5613D038.7000803@oracle.com> (raw)
In-Reply-To: <20151006132138.GB28743@rei.suse.cz>
Hi,
On 10/06/2015 04:21 PM, Cyril Hrubis wrote:
> Hi!
>> testcases/network/nfs/nfs_stress/open_files.c | 126 +++++++++++++++++++++++++
> I would like to to see the open_files.c to be renamed to
> nfs01_open_files.c.
OK, I'll rename it.
Thanks,
Alexey
> Otherwise the patchset looks good, acked.
>
next prev parent reply other threads:[~2015-10-06 13:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-30 13:09 [LTP] [PATCH 01/10 resend] network/nfs01: add IPv6 test-cases Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 02/10] network/nfs: rename nfs dir to nfs_stress Alexey Kodanev
2015-10-06 13:21 ` Cyril Hrubis
2015-10-06 13:44 ` Alexey Kodanev [this message]
2015-10-07 10:22 ` Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 03/10] network/nfs_stress: move common code from nfs01 to library Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 04/10] network/nfs02: move to nfs_stress Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 05/10] network/nfs_stress/nfs02: use nfs_lib.sh Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 06/10] network/nfs/nfs_stress: rename library functions names Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 07/10] network/nfs03: move to nfs_stress directory Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 08/10] network/nfs_stress/nfs03: use nfs_lib.sh, run over IPv6 Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 09/10] network/nfs04: move to nfs_stress directory Alexey Kodanev
2015-09-30 13:09 ` [LTP] [PATCH 10/10] network/nfs04: cleanup and use nfs_lib.sh Alexey Kodanev
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=5613D038.7000803@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.