[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180121125936.GA17395@krava>
Date: Sun, 21 Jan 2018 13:59:36 +0100
From: Jiri Olsa <jolsa@...hat.com>
To: kan.liang@...el.com
Cc: acme@...nel.org, peterz@...radead.org, mingo@...hat.com,
linux-kernel@...r.kernel.org, wangnan0@...wei.com,
jolsa@...nel.org, namhyung@...nel.org, ak@...ux.intel.com,
yao.jin@...ux.intel.com
Subject: Re: [PATCH V5 00/17] perf top overwrite mode
On Thu, Jan 18, 2018 at 01:26:15PM -0800, kan.liang@...el.com wrote:
> From: Kan Liang <kan.liang@...el.com>
>
> ------
> Changes since V4:
> - Added a bug fix patch which recalculate the 'size' in
> perf_mmap__push()
> - Added a cleanup patch for perf_mmap__push()
> - Modified the patch which introduce perf_mmap__read_init()
> - Added a patch to change return value logic for perf_mmap__read_init()
> - Dropped the unnecessary refcnt check in perf_mmap__read_init()
> The check will be done later in perf_mmap__read_event().
> - Used warn_lost_event to replace !no_lost_event_warning
Acked-by: Jiri Olsa <jolsa@...nel.org>
thanks,
jirka
Powered by blists - more mailing lists