From: Namhyung Kim <namhyung@kernel.org>
To: Wang Nan <wangnan0@huawei.com>
Cc: linux-kernel@vger.kernel.org, kan.liang@intel.com,
acme@kernel.org, jolsa@redhat.com, zhangmengting@huawei.com,
kernel-team@lge.com
Subject: Re: [PATCH v3 0/3] perf tools: perf tools: Clarify overwrite and backward, bugfix
Date: Tue, 5 Dec 2017 09:04:33 +0900 [thread overview]
Message-ID: <20171205000433.GA16663@sejong> (raw)
In-Reply-To: <20171204165107.95327-1-wangnan0@huawei.com>
On Mon, Dec 04, 2017 at 04:51:04PM +0000, Wang Nan wrote:
> Simplify patch 1/3 following Namhyung's suggestion.
>
> Context adjustment for patch 2 and 3.
>
> Wang Nan (3):
> perf mmap: Fix perf backward recording
> perf tools: Don't discard prev in backward mode
> perf tools: Replace 'backward' to 'overwrite' in evlist. mmap and
> record
Acked-by: Namhyung Kim <namhyung@kernel.org>
Thanks,
Namhyung
>
> tools/perf/builtin-record.c | 14 +++++-----
> tools/perf/tests/backward-ring-buffer.c | 4 +--
> tools/perf/util/evlist.c | 41 +++++++++++++++++-------------
> tools/perf/util/evlist.h | 2 +-
> tools/perf/util/mmap.c | 45 +++++++++++++++------------------
> 5 files changed, 54 insertions(+), 52 deletions(-)
>
> --
> 2.10.1
>
prev parent reply other threads:[~2017-12-05 0:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-04 16:51 [PATCH v3 0/3] perf tools: perf tools: Clarify overwrite and backward, bugfix Wang Nan
2017-12-04 16:51 ` [PATCH v3 1/3] perf mmap: Fix perf backward recording Wang Nan
2017-12-06 16:44 ` [tip:perf/core] " tip-bot for Wang Nan
2017-12-04 16:51 ` [PATCH v3 2/3] perf tools: Don't discard prev in backward mode Wang Nan
2017-12-06 16:45 ` [tip:perf/core] perf mmap: " tip-bot for Wang Nan
2017-12-04 16:51 ` [PATCH v3 3/3] perf tools: Replace 'backward' to 'overwrite' in evlist. mmap and record Wang Nan
2017-12-06 16:45 ` [tip:perf/core] perf tools: Rename 'backward' to 'overwrite' in evlist, " tip-bot for Wang Nan
2017-12-05 0:04 ` Namhyung Kim [this message]
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=20171205000433.GA16663@sejong \
--to=namhyung@kernel.org \
--cc=acme@kernel.org \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=kernel-team@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wangnan0@huawei.com \
--cc=zhangmengting@huawei.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