ltp.lists.linux.it archive mirror
 help / color / mirror / Atom feed
From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH] [RFC] tst_test: Add support for array of test	functions
Date: Tue, 3 Oct 2017 03:58:17 -0400 (EDT)	[thread overview]
Message-ID: <860483630.25581747.1507017497043.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20170727081437.27995-1-chrubis@suse.cz>



----- Original Message -----
> This commits add third option for specifying the test functions in an
> NULL terminated array of function pointers + converts two testcases.

Hi,

What would be the benefits?

- it's almost same amount of code
- it makes tst_test interface bit more complicated
- as a user I'd probably go with test_all(), since it's most straight-forward
- if those test funcs have parameter other than void, you still need
  to use the old way

Regards,
Jan

  parent reply	other threads:[~2017-10-03  7:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-27  8:14 [LTP] [PATCH] [RFC] tst_test: Add support for array of test functions Cyril Hrubis
2017-10-02 13:16 ` Cyril Hrubis
2017-10-03  7:58 ` Jan Stancek [this message]
2017-10-03 12:59   ` Cyril Hrubis

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=860483630.25581747.1507017497043.JavaMail.zimbra@redhat.com \
    --to=jstancek@redhat.com \
    --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;
as well as URLs for NNTP newsgroup(s).