From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH v2 2/2] Reimplement TST_SAFE_TIMERFD_*() using TST_ASSERT_SYSCALL*()
Date: Thu, 5 Mar 2020 16:20:33 +0100 [thread overview]
Message-ID: <20200305152033.GA1160@rei.lan> (raw)
In-Reply-To: <20200305151459.30341-2-mdoucha@suse.cz>
Hi!
> lib/tst_safe_timerfd.c | 35 ++++++-----------------------------
> 1 file changed, 6 insertions(+), 29 deletions(-)
>
> diff --git a/lib/tst_safe_timerfd.c b/lib/tst_safe_timerfd.c
> index ffe7b2ef7..8c042f8c8 100644
> --- a/lib/tst_safe_timerfd.c
> +++ b/lib/tst_safe_timerfd.c
> @@ -9,34 +9,18 @@
> #define TST_NO_DEFAULT_MAIN
> #include "tst_test.h"
>
> -#define TTYPE (errno == ENOTSUP ? TCONF : TBROK)
> -
> int safe_timerfd_create(const char *file, const int lineno,
> int clockid, int flags)
> {
> - int fd;
> -
> - fd = timerfd_create(clockid, flags);
> - if (fd < 0) {
> - tst_brk(TTYPE | TERRNO, "%s:%d timerfd_create(%s) failed",
> - file, lineno, tst_clock_name(clockid));
> - }
> -
> - return fd;
> + return TST_ASSERT_SYSCALL_FD_IMPL(timerfd_create(clockid, flags), file,
> + lineno, "timerfd_create(%s)", tst_clock_name(clockid));
> }
Well at this point we basically pass everything that has been in the
function to the macro. So we do not save much on typing, the code is not
simpler and the obvious and readable code we had has been turned into a
macro. I do not think that this is improvement.
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2020-03-05 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 15:14 [LTP] [PATCH v2 1/2] Add TST_ASSERT_SYSCALL*() macros Martin Doucha
2020-03-05 15:14 ` [LTP] [PATCH v2 2/2] Reimplement TST_SAFE_TIMERFD_*() using TST_ASSERT_SYSCALL*() Martin Doucha
2020-03-05 15:20 ` Cyril Hrubis [this message]
2020-03-05 17:50 ` Petr Vorel
2020-03-05 17:42 ` [LTP] [PATCH v2 1/2] Add TST_ASSERT_SYSCALL*() macros Petr Vorel
2020-03-05 17:53 ` Cyril Hrubis
2020-03-05 19:36 ` Petr Vorel
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=20200305152033.GA1160@rei.lan \
--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