linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jes Sorensen <jes.sorensen@gmail.com>
To: Zhilong Liu <zlliu@suse.com>
Cc: linux-raid@vger.kernel.org
Subject: Re: [PATCH 2/3 v1] mdadm/test: Refactor the codes of 'test' script
Date: Fri, 9 Jun 2017 11:05:35 -0400	[thread overview]
Message-ID: <a9a775d0-8c42-35a1-17cc-0ab17aaeccab@gmail.com> (raw)
In-Reply-To: <1496913628-22779-1-git-send-email-zlliu@suse.com>

On 06/08/2017 05:20 AM, Zhilong Liu wrote:
> Adding functions:
> die()
>    uniform the abnormal situations that have to abort.
> check_env()
>    do various basic checking before running test suite.
> save_log()
>    collect array infos, include of dmesg, superblock,
>    bitmap and /proc/mdstat.
> main()
>    the core function of this script.
> 
> Improve functions:
> cleanup()
>    clear dmesg and remove the /vat/tmp/mdtest* files.
> mdadm()
>    clear superblock once creating or building arrays
>    every time, because it's always creating arrays
>    many times in a test case.
> check()
>    just tidy up with die(), didn't change code meanings.
> testdev()
>    add checking $1 must be a block device, add 'return 0'
>    in final because this function exists in last line of
>    test case, such as tests/05r6tor0.
> do_test()
>    add checking abnormal dmesg and changing log management.
> do_help()
>    just recommend a better way to print Usage.
> parse_args()
>    just tidy up.
> 
> Signed-off-by: Zhilong Liu <zlliu@suse.com>
> ---
>   test | 346 +++++++++++++++++++++++++++++++++++++------------------------------
>   1 file changed, 191 insertions(+), 155 deletions(-)

Zhilong,

When sending out a v2 please add a small comment below the --- 
explaining what you changed.

Cheers,
Jes


PS: I note you start with v1 for updates, but v1 is really the first 
version - not a big deal.

  reply	other threads:[~2017-06-09 15:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07  9:31 [PATCH 0/3] mdadm/test: Refactor the codes of 'test' script Zhilong Liu
2017-06-07  9:31 ` [PATCH 1/3] mdadm/test: Convert code format to use Tab Zhilong Liu
2017-06-09 15:06   ` Jes Sorensen
2017-06-07  9:31 ` [PATCH 2/3] mdadm/test: Refactor the codes of 'test' script Zhilong Liu
2017-06-08  9:20   ` [PATCH 2/3 v1] " Zhilong Liu
2017-06-09 15:05     ` Jes Sorensen [this message]
2017-06-07  9:31 ` [PATCH 3/3] mdadm/test: Get rid of fast_sync() Zhilong Liu
2017-06-09 15:08 ` [PATCH 0/3] mdadm/test: Refactor the codes of 'test' script Jes Sorensen
2017-06-12  2:32   ` Zhilong Liu

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=a9a775d0-8c42-35a1-17cc-0ab17aaeccab@gmail.com \
    --to=jes.sorensen@gmail.com \
    --cc=linux-raid@vger.kernel.org \
    --cc=zlliu@suse.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;
as well as URLs for NNTP newsgroup(s).