From: chrubis@suse.cz
To: Mats Liljegren <mats.liljegren@enea.com>
Cc: ltp-list@lists.sourceforge.net, Kevin Hilman <khilman@linaro.org>,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [LTP] [PATCH v3] partrt_nohz_full: Introducing a new test case
Date: Tue, 3 Jun 2014 13:31:56 +0200 [thread overview]
Message-ID: <20140603113156.GA26233@rei.Home> (raw)
In-Reply-To: <20140603104018.3b0cba6f@mats-desktop>
Hi!
> I could change partrt to accept CPU list directly instead of being
> dependent on list2mask tool, which means that list2mask disappears.
>
> As for count_ticks, a better name might be kernel_ticks.
> count_kernel_ticks would be possible but is a bit too long for me...
>
> Would having the tool names
>
> partrt
> kernel_ticks
>
> be good enough for ltp, or do you want kernel_ticks prefixed? If so,
> I'd propose:
>
> partrt
> partrt_kernel_ticks
>
> In this case the original name kernel_ticks will be renamed for ltp
> only.
>
> What do you prefer?
Prefixing with partrt_ for LTP (upon installation) sounds good to me.
--
Cyril Hrubis
chrubis@suse.cz
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and their
applications. Written by three acclaimed leaders in the field,
this first edition is now available. Download your free book today!
http://p.sf.net/sfu/NeoTech
_______________________________________________
Ltp-list mailing list
Ltp-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ltp-list
next prev parent reply other threads:[~2014-06-03 11:32 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 13:50 [LTP] Testing absence of ticks with nohz_full Mats Liljegren
2014-03-10 14:04 ` chrubis
2014-03-10 15:17 ` Frederic Weisbecker
2014-03-10 15:27 ` Steven Rostedt
2014-03-10 15:33 ` Frederic Weisbecker
2014-03-11 10:34 ` Mats Liljegren
2014-03-11 23:31 ` Steven Rostedt
2014-03-13 22:10 ` Kevin Hilman
2014-03-17 16:35 ` Mats Liljegren
2014-04-16 15:48 ` [LTP] [RFC][PATCH] partrt_nohz_full: Introducing a new test case Mats Liljegren
2014-04-16 15:48 ` Mats Liljegren
2014-04-22 15:47 ` chrubis
[not found] ` <20140423124410.29874232@mats-desktop>
2014-04-23 11:34 ` chrubis
[not found] ` <20140424105218.5cd2b5bf@mats-desktop>
2014-04-24 9:06 ` chrubis
[not found] ` <20140424140358.63dac752@mats-desktop>
2014-04-24 12:35 ` chrubis
2014-04-22 14:07 ` chrubis
[not found] ` <20140423084101.536f03f0@mats-desktop>
2014-04-23 10:24 ` chrubis
2014-04-28 15:06 ` [LTP] [PATCH v2] " Mats Liljegren
2014-04-28 15:06 ` [LTP] [PATCH] " Mats Liljegren
2014-05-06 16:20 ` chrubis
[not found] ` <20140507132016.40361a0a@mats-desktop>
2014-05-07 12:17 ` chrubis
2014-05-13 14:11 ` [LTP] [PATCH v3] " Mats Liljegren
2014-05-13 14:11 ` Mats Liljegren
2014-06-02 17:17 ` chrubis
[not found] ` <20140603104018.3b0cba6f@mats-desktop>
2014-06-03 11:31 ` chrubis [this message]
[not found] ` <20141030171737.3eb800f1@mats-desktop>
2014-11-26 13:40 ` Cyril Hrubis
2014-05-28 16:45 ` Mats Liljegren
2014-05-29 12:21 ` chrubis
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=20140603113156.GA26233@rei.Home \
--to=chrubis@suse.cz \
--cc=fweisbec@gmail.com \
--cc=khilman@linaro.org \
--cc=ltp-list@lists.sourceforge.net \
--cc=mats.liljegren@enea.com \
/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