From: chrubis@suse.cz
To: "zenglg.jy" <zenglg.jy@cn.fujitsu.com>
Cc: ltp-list <ltp-list@lists.sourceforge.net>
Subject: Re: [LTP] [PATCH] clock_getres/clock_getres01.c: cleanup
Date: Wed, 6 Nov 2013 13:53:17 +0100 [thread overview]
Message-ID: <20131106124955.GC28897@rei> (raw)
In-Reply-To: <1383710112.1600.3.camel@localhost>
Hi!
> Fix the messy testcase of clock_getres01.c
>
> Signed-off-by: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
That's better that the previous state but there are still some things to
fix:
1. The options are unused (opt_debug is only set and never used)
we can strip all the custom option parsing and remove the usage()
function and add LTP standard:
char *msg;
if ((msg = parse_opts(ac, av, NULL, NULL)) != NULL)
tst_brkm(TBROK, NULL, "OPTION PARSING ERROR - %s", msg);
2. Does the test really need to create temporary directory?
It does not seem to create any files, so we can remove the
tst_tmpdir() and tst_rmdir() in cleanup() and setup().
Also I would sanitize the comments in test header so that the ending */ does
not overflow 80 chars and end up on the same column. (May need to move the word Foundation to the previous line)
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniques for threading, error checking, porting, and tuning. Get the most
from the latest Intel processors and coprocessors. See abstracts and register
http://pubads.g.doubleclick.net/gampad/clk?id=60136231&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
parent reply other threads:[~2013-11-06 16:36 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <1383710112.1600.3.camel@localhost>]
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=20131106124955.GC28897@rei \
--to=chrubis@suse.cz \
--cc=ltp-list@lists.sourceforge.net \
--cc=zenglg.jy@cn.fujitsu.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