From: David Ahern <dsahern@gmail.com>
To: Borislav Petkov <bp@alien8.de>, LKML <linux-kernel@vger.kernel.org>
Cc: Borislav Petkov <bp@suse.de>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Robert Richter <rric@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Namhyung Kim <namhyung@gmail.com>,
Steven Rostedt <rostedt@goodmis.org>,
Stanislav Fomichev <stfomichev@yandex-team.ru>,
Stephane Eranian <eranian@google.com>,
Andi Kleen <ak@linux.intel.com>,
Arjan van de Ven <arjan@linux.intel.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Mike Galbraith <efault@gmx.de>, Pekka Enberg <penberg@kernel.org>,
Paul Mackerras <paulus@samba.org>
Subject: Re: [PATCH 1/2] tools/: Convert to new topic libraries
Date: Tue, 10 Dec 2013 18:46:15 -0700 [thread overview]
Message-ID: <52A7C3E7.301@gmail.com> (raw)
In-Reply-To: <1386605664-24041-2-git-send-email-bp@alien8.de>
On 12/9/13, 9:14 AM, Borislav Petkov wrote:
> From: Borislav Petkov <bp@suse.de>
>
> Move debugfs.* to api/fs/. We have a common tools/lib/api/ place
> where the Makefile lives and then we place the headers in subdirs.
> For example, all the fs-related stuff goes to tools/lib/api/fs/ from
> which we get libapikfs.a (acme got almost the naming he wanted :-))
> and we link it into the tools which need it - in this case perf and
> tools/vm/page-types.
>
> acme:
>
> "Looking at the implementation, I think some tools can even link
> directly to the .o files, avoiding the .a file altogether.
>
> But that is just an optimization/finer granularity tools/lib/
> cherrypicking that toolers can make use of."
>
> Fixup documentation cleaning target while at it.
>
no longer applies to the moving target that is acme's tree.
David
next prev parent reply other threads:[~2013-12-11 1:46 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-09 16:14 [PATCH -v1.1 0/2] perf tool: Carve out fs.* stuff Borislav Petkov
2013-12-09 16:14 ` [PATCH 1/2] tools/: Convert to new topic libraries Borislav Petkov
2013-12-10 1:32 ` Namhyung Kim
2013-12-10 11:27 ` Borislav Petkov
2013-12-11 1:21 ` Namhyung Kim
2013-12-11 12:31 ` Arnaldo Carvalho de Melo
2013-12-11 1:46 ` David Ahern [this message]
2013-12-11 9:56 ` Borislav Petkov
2013-12-11 12:31 ` Arnaldo Carvalho de Melo
2013-12-11 13:24 ` Ingo Molnar
2013-12-11 13:30 ` Borislav Petkov
2013-12-11 13:54 ` Arnaldo Carvalho de Melo
2013-12-11 14:02 ` Borislav Petkov
2013-12-18 10:30 ` [tip:perf/core] " tip-bot for Borislav Petkov
2013-12-09 16:14 ` [PATCH 2/2] perf: Move fs.* to lib/api/fs/ Borislav Petkov
2013-12-16 13:37 ` Arnaldo Carvalho de Melo
2014-02-22 17:59 ` [tip:perf/core] perf tools: " tip-bot for Borislav Petkov
-- strict thread matches above, loose matches on Subject: below --
2013-12-05 16:25 [PATCH 0/2] perf tool: Carve out fs.* stuff Borislav Petkov
2013-12-05 16:25 ` [PATCH 1/2] tools/: Convert to new topic libraries Borislav Petkov
2013-12-09 10:22 ` Jiri Olsa
2013-12-09 10:42 ` Borislav Petkov
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=52A7C3E7.301@gmail.com \
--to=dsahern@gmail.com \
--cc=acme@infradead.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=arjan@linux.intel.com \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=efault@gmx.de \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@gmail.com \
--cc=paulus@samba.org \
--cc=penberg@kernel.org \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=rric@kernel.org \
--cc=stfomichev@yandex-team.ru \
/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).