From: Tony Jones <tonyj@suse.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Vlastimil Babka <vbabka@suse.cz>
Cc: linux-kernel@vger.kernel.org, linux-perf-users@vger.kernel.org,
Mel Gorman <mgorman@suse.com>
Subject: Re: [PATCH v2] perf script/python: add new compaction-times script
Date: Fri, 21 Aug 2015 08:56:39 -0700 [thread overview]
Message-ID: <55D74A37.5020104@suse.com> (raw)
In-Reply-To: <20150820194242.GD3154@kernel.org>
On 08/20/2015 12:42 PM, Arnaldo Carvalho de Melo wrote:
> Well, we don't have any firm set standard for outputting from scripts,
> so if you did it inspired by existing scripts outputs, probably that is
> good enough, having someone testing it is a plus, and in these cases, if
> the "works for me" means you actually tested it, can we replace the
> "Acked-by" with a "Tested-by"?
The output seemed consistent with the existing scripts in that, as you point out, there really isn't much consistency. Taking a second look, the only thing I can see is that scripts such as futex-contention and failed-syscalls-by-pid output "comm *[pid]" whereas I'm outputting "pid[comm]". That's certainly easy to change.
Yes, I believe Vlastimil tested v1 and v2 but I'll let him speak to this and to whether his approval goes beyond testing (re: acked-by).
thanks
tony
next prev parent reply other threads:[~2015-08-21 15:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-06 23:01 [PATCH] perf script/python: add new compaction-times script Tony Jones
2015-08-11 9:13 ` Vlastimil Babka
2015-08-17 19:48 ` [PATCH v2] " Tony Jones
2015-08-20 9:33 ` Vlastimil Babka
2015-08-20 19:42 ` Arnaldo Carvalho de Melo
2015-08-21 15:56 ` Tony Jones [this message]
2015-08-21 18:05 ` Vlastimil Babka
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=55D74A37.5020104@suse.com \
--to=tonyj@suse.com \
--cc=acme@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mgorman@suse.com \
--cc=vbabka@suse.cz \
/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).