From: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
To: ltp-list@lists.sourceforge.net
Subject: [LTP] [PATCH] clock_getres/clock_getres01.c: Add CLOCK_MONOTONIC_RAW test
Date: Thu, 31 Oct 2013 16:11:43 +0800 [thread overview]
Message-ID: <527210BF.3040803@cn.fujitsu.com> (raw)
Add CLOCK_MONOTONIC_RAW test in clock_getres01.c for clock_getres(2)
Signed-off-by: Zeng Linggang <zenglg.jy@cn.fujitsu.com>
---
testcases/kernel/syscalls/clock_getres/clock_getres01.c | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/testcases/kernel/syscalls/clock_getres/clock_getres01.c b/testcases/kernel/syscalls/clock_getres/clock_getres01.c
index 0fb5df4..c73b0ce 100644
--- a/testcases/kernel/syscalls/clock_getres/clock_getres01.c
+++ b/testcases/kernel/syscalls/clock_getres/clock_getres01.c
@@ -188,6 +188,12 @@ static struct test_case tcase[] = {
.ret = 0,
.err = 0,
},
+ {
+ .clk_id = CLOCK_MONOTONIC_RAW,
+ .ttype = NORMAL,
+ .ret = 0,
+ .err = 0,
+ },
};
#define MEM_LENGTH (4 * 1024 * 1024)
-- 1.8.2.1
------------------------------------------------------------------------------
Android is increasing in popularity, but the open development platform that
developers love is also attractive to malware creators. Download this white
paper to learn more about secure code signing practices that can help keep
Android apps secure.
http://pubads.g.doubleclick.net/gampad/clk?id=65839951&iu=/4140/ostg.clktrk
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next reply other threads:[~2013-10-31 8:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-31 8:11 Zeng Linggang [this message]
2013-10-31 15:49 ` [LTP] [PATCH] clock_getres/clock_getres01.c: Add CLOCK_MONOTONIC_RAW test chrubis
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=527210BF.3040803@cn.fujitsu.com \
--to=zenglg.jy@cn.fujitsu.com \
--cc=ltp-list@lists.sourceforge.net \
/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