[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191021160811.GI32718@krava>
Date: Mon, 21 Oct 2019 18:08:11 +0200
From: Jiri Olsa <jolsa@...hat.com>
To: Jin Yao <yao.jin@...ux.intel.com>
Cc: acme@...nel.org, jolsa@...nel.org, peterz@...radead.org,
mingo@...hat.com, alexander.shishkin@...ux.intel.com,
Linux-kernel@...r.kernel.org, ak@...ux.intel.com,
kan.liang@...el.com, yao.jin@...el.com
Subject: Re: [PATCH v2 1/5] perf util: Create new block.h/block.c for block
related functions
On Tue, Oct 15, 2019 at 01:33:46PM +0800, Jin Yao wrote:
SNIP
> diff --git a/tools/perf/util/Build b/tools/perf/util/Build
> index 39814b1806a6..3121c0055950 100644
> --- a/tools/perf/util/Build
> +++ b/tools/perf/util/Build
> @@ -1,4 +1,5 @@
> perf-y += annotate.o
> +perf-y += block.o
> perf-y += block-range.o
> perf-y += build-id.o
> perf-y += cacheline.o
> diff --git a/tools/perf/util/block.c b/tools/perf/util/block.c
> new file mode 100644
> index 000000000000..e5e6f941f040
> --- /dev/null
> +++ b/tools/perf/util/block.c
please use block_info.c, block.c is misleading wrt what
we are doing here..
jirka
Powered by blists - more mailing lists