From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v3 1/2] lib: include SAFE_CLOCK_ADJTIME() macro
Date: Wed, 13 Mar 2019 17:09:41 +0100 [thread overview]
Message-ID: <20190313160941.GB6171@rei> (raw)
In-Reply-To: <20190226160804.16596-1-rafael.tinoco@linaro.org>
Hi!
> +static inline void safe_clock_adjtime(const char *file, const int lineno,
> + clockid_t clk_id, struct timex *txc)
> +{
> + int rval;
> +
> + rval = tst_syscall(__NR_clock_adjtime, clk_id, txc);
Any reason why we don't use clock_adjtime() here?
Or is the glibc wrapper missing?
> + if (rval != 0)
> + tst_brk(TBROK | TERRNO,
> + "%s:%d clock_adjtime() failed", file, lineno);
> +}
> #define SAFE_CLOCK_GETRES(clk_id, res)\
> safe_clock_getres(__FILE__, __LINE__, (clk_id), (res))
>
> @@ -50,3 +63,6 @@ static inline void safe_clock_settime(const char *file, const int lineno,
>
> #define SAFE_CLOCK_SETTIME(clk_id, tp)\
> safe_clock_settime(__FILE__, __LINE__, (clk_id), (tp))
> +
> +#define SAFE_CLOCK_ADJTIME(clk_id, txc)\
> + safe_clock_adjtime(__FILE__, __LINE__, (clk_id), (txc))
> --
> 2.20.1
>
>
> --
> Mailing list info: https://lists.linux.it/listinfo/ltp
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-03-13 16:09 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 20:05 [LTP] [PATCH 1/2] lib: include SAFE_CLOCK_ADJTIME() macro Rafael David Tinoco
2019-02-21 20:05 ` [LTP] [PATCH 2/2] syscalls/clock_adjtime: create clock_adjtime syscall tests Rafael David Tinoco
2019-02-21 20:19 ` Rafael David Tinoco
2019-02-21 20:30 ` [LTP] [PATCH v2 1/2] lib: include SAFE_CLOCK_ADJTIME() macro Rafael David Tinoco
2019-02-21 20:30 ` [LTP] [PATCH v2 2/2] syscalls/clock_adjtime: create clock_adjtime syscall tests Rafael David Tinoco
2019-02-26 0:17 ` Petr Vorel
2019-02-26 0:24 ` Enji Cooper
2019-02-26 16:08 ` [LTP] [PATCH v3 1/2] lib: include SAFE_CLOCK_ADJTIME() macro Rafael David Tinoco
2019-02-26 16:08 ` [LTP] [PATCH v3 2/2] syscalls/clock_adjtime: create clock_adjtime syscall tests Rafael David Tinoco
2019-03-13 16:32 ` Cyril Hrubis
2019-03-15 11:07 ` Rafael David Tinoco
2019-03-20 21:41 ` [LTP] [PATCH v2 1/3] lib: include SAFE_CLOCK_ADJTIME() macro Rafael David Tinoco
2019-03-20 21:41 ` [LTP] [PATCH v2 2/3] lapi/posix_clocks.h: add MAX_CLOCKS definition Rafael David Tinoco
2019-03-20 21:41 ` [LTP] [PATCH v2 3/3] syscalls/clock_adjtime: create clock_adjtime syscall tests Rafael David Tinoco
2019-03-20 21:48 ` Rafael David Tinoco
2019-03-21 13:42 ` Cyril Hrubis
2019-03-21 13:57 ` Rafael David Tinoco
2019-03-21 14:05 ` Cyril Hrubis
2019-03-21 14:10 ` Cyril Hrubis
2019-03-21 14:17 ` Rafael David Tinoco
2019-03-21 20:27 ` [LTP] [PATCH v3 1/4] lib: include SAFE_CLOCK_ADJTIME() macro Rafael David Tinoco
2019-03-21 20:27 ` [LTP] [PATCH v3 2/4] lib: Add include guard to tst_safe_clocks.h Rafael David Tinoco
2019-03-21 20:27 ` [LTP] [PATCH v3 3/4] lapi/posix_clocks.h: add MAX_CLOCKS definition Rafael David Tinoco
2019-03-21 20:27 ` [LTP] [PATCH v3 4/4] syscalls/clock_adjtime: create clock_adjtime syscall tests Rafael David Tinoco
2019-03-21 20:31 ` Rafael David Tinoco
2019-03-22 13:34 ` Cyril Hrubis
2019-03-22 13:36 ` Rafael David Tinoco
2019-03-22 18:25 ` [LTP] [PATCH v4 1/4] lib: include SAFE_CLOCK_ADJTIME() macro Rafael David Tinoco
2019-03-22 18:25 ` [LTP] [PATCH v4 2/4] lib: Add include guard to tst_safe_clocks.h Rafael David Tinoco
2019-03-22 18:25 ` [LTP] [PATCH v4 3/4] lapi/posix_clocks.h: add MAX_CLOCKS definition Rafael David Tinoco
2019-03-22 18:25 ` [LTP] [PATCH v4 4/4] syscalls/clock_adjtime: create clock_adjtime syscall tests Rafael David Tinoco
2019-03-25 16:24 ` [LTP] [PATCH v4 1/4] lib: include SAFE_CLOCK_ADJTIME() macro Cyril Hrubis
2019-03-21 13:54 ` [LTP] [PATCH v2 3/3] syscalls/clock_adjtime: create clock_adjtime syscall tests Cyril Hrubis
2019-03-21 14:00 ` Rafael David Tinoco
2019-03-21 14:06 ` Cyril Hrubis
2019-03-13 16:09 ` Cyril Hrubis [this message]
2019-03-13 16:26 ` [LTP] [PATCH v3 1/2] lib: include SAFE_CLOCK_ADJTIME() macro Rafael David Tinoco
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=20190313160941.GB6171@rei \
--to=chrubis@suse.cz \
--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