From: Peter Zijlstra <a.p.zijlstra@chello.nl>
To: avagin@gmail.com
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Andrew Vagin <avagin@openvz.org>,
linux-kernel@vger.kernel.org, paulus@samba.org, mingo@elte.hu,
asharma@fb.com, devel@openvz.org, dsahern@gmail.com,
linux-perf-users@vger.kernel.org
Subject: Re: [PATCH 3/6] perf: add ability to record event period
Date: Tue, 20 Dec 2011 11:17:28 +0100 [thread overview]
Message-ID: <1324376248.24621.26.camel@twins> (raw)
In-Reply-To: <4EF0424D.3070102@gmail.com>
On Tue, 2011-12-20 at 12:07 +0400, Andrew Vagin wrote:
> Look at the comment below. In it I try describe why we need this
> functionality.
Its not about comments, a patch has to have a Changelog that covers the
why and what. If it doesn't the patch won't go anywhere. Also, its not
the maintainers job to reconstruct such a changelog from an email
discussion.
So write up a proper changelog and resubmit the patch.
next prev parent reply other threads:[~2011-12-20 10:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-07 13:55 [PATCH 0/7] Profiling sleep times (v4) Andrew Vagin
2011-12-07 13:55 ` [PATCH 1/6] perf: use event_name() to get an event name Andrew Vagin
2011-12-07 13:55 ` [PATCH 2/6] perf: add ability to change event according to sample (v3) Andrew Vagin
2011-12-07 13:55 ` [PATCH 3/6] perf: add ability to record event period Andrew Vagin
2011-12-16 7:13 ` Andrew Vagin
2011-12-19 19:20 ` Arun Sharma
2011-12-19 20:58 ` Arnaldo Carvalho de Melo
2011-12-19 21:25 ` David Ahern
2011-12-20 8:07 ` Andrew Vagin
2011-12-20 10:17 ` Peter Zijlstra [this message]
2011-12-20 13:26 ` Arnaldo Carvalho de Melo
2011-12-07 13:55 ` [PATCH 4/6] perf: teach "perf inject" to work with files Andrew Vagin
2011-12-07 13:56 ` [PATCH 5/6] perf: teach perf inject to merge sched_stat_* and sched_switch events Andrew Vagin
2011-12-07 13:56 ` [PATCH 6/6] perf: add scripts for profiling sleep times (v2) Andrew Vagin
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=1324376248.24621.26.camel@twins \
--to=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=asharma@fb.com \
--cc=avagin@gmail.com \
--cc=avagin@openvz.org \
--cc=devel@openvz.org \
--cc=dsahern@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
/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).