From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [RFC PATCH 1/4] syscalls/abort01: convert to new library
Date: Tue, 26 Mar 2019 13:51:32 +0100 [thread overview]
Message-ID: <20190326125132.GA11086@rei.lan> (raw)
In-Reply-To: <20190326124743.GC5826@google.com>
Hi!
> > * Got rid of tst_brk(TFAIL, ...) calls
> > see: https://github.com/linux-test-project/ltp/issues/462
>
> Thanks for this, it is good to know. What is the recommended replacement?
> tst_res()?
Yes, tst_res() followed by either return or exit(0) if you need to
actually exit the code flow.
> >
> > * Used tst_strsig() and tst_strstatus() to print signal and status
> >
> > * Used tst_res() API in the child
> >
> > * Got rid of unused variables, etc.
>
> I am surprised that didn't throw a warning + build error for me.
> other than that, thanks for doing this
That depends on gcc version and mix of warning flags...
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-03-26 12:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-25 23:20 [LTP] [PATCH 0/4] Convert tests to use new library Sandeep Patil
2019-03-25 23:20 ` [LTP] [RFC PATCH 1/4] syscalls/abort01: convert to " Sandeep Patil
2019-03-26 11:58 ` Cyril Hrubis
2019-03-26 12:47 ` Sandeep Patil
2019-03-26 12:51 ` Cyril Hrubis [this message]
2019-03-28 4:07 ` Sandeep Patil
2019-04-03 12:06 ` Cyril Hrubis
2019-04-03 15:49 ` Sandeep Patil
2019-03-25 23:20 ` [LTP] [PATCH 2/4] syscalls/accept01: " Sandeep Patil
2019-03-26 12:35 ` Cyril Hrubis
2019-03-26 12:44 ` Sandeep Patil
2019-03-25 23:20 ` [LTP] [PATCH 3/4] syscalls/accept4: " Sandeep Patil
2019-03-26 15:33 ` Cyril Hrubis
2019-03-25 23:20 ` [LTP] [PATCH 4/4] syscalls/acct01: " Sandeep Patil
2019-03-26 16:11 ` Cyril Hrubis
2019-03-26 9:42 ` [LTP] [PATCH 0/4] Convert tests to use " Cyril Hrubis
2019-03-26 12:48 ` Sandeep Patil
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=20190326125132.GA11086@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.