From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] C API: Turn .test_variants into array of description
Date: Tue, 19 May 2020 16:35:25 +0200 [thread overview]
Message-ID: <20200519143525.GA8076@dell5510> (raw)
In-Reply-To: <20200519140704.GE16008@yuki.lan>
Hi Cyril,
> I do not think that having more ifdefs and splitting the test variant
> structure helps to make things simple in the case of timer testcases.
> What exact problem are you trying to solve?
Well, no real problem, just less code in tests.
OK, let's drop this attempt.
Kind regards,
Petr
next prev parent reply other threads:[~2020-05-19 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 12:07 [LTP] [PATCH 1/1] C API: Turn .test_variants into array of description Petr Vorel
2020-05-19 14:07 ` Cyril Hrubis
2020-05-19 14:35 ` Petr Vorel [this message]
2020-05-20 4:40 ` Viresh Kumar
2020-05-20 5:48 ` 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=20200519143525.GA8076@dell5510 \
--to=pvorel@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