From: Arnaldo Carvalho de Melo <acme@infradead.org>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>, Borislav Petkov <bp@suse.de>,
Ingo Molnar <mingo@kernel.org>, Jiri Olsa <jolsa@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Robert Richter <rric@kernel.org>, David Ahern <dsahern@gmail.com>,
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>
Date: Thu, 5 Dec 2013 14:45:33 -0300 [thread overview]
Message-ID: <20131205174533.GE10333@ghostprotocols.net> (raw)
echo Link: http://lkml.kernel.org/n/tip-`ranpwd -l 24`@git.kernel.org
Bcc:
Subject: Re: [PATCH 0/2] perf tool: Carve out fs.* stuff
Reply-To:
In-Reply-To: <1386260752-16436-1-git-send-email-bp@alien8.de>
X-Url: http://acmel.wordpress.com
Em Thu, Dec 05, 2013 at 05:25:50PM +0100, Borislav Petkov escreveu:
> From: Borislav Petkov <bp@suse.de>
>
> Ok,
>
> step one: carve out fs-related stuff into a libapikfs.a library.
Adding some more people to the CC list, but from a quick look, this
is in line with what we discussed so far, so I'm ok with it.
For those people in the CC list, Acked-by would be really, really
appreciated.
- Arnaldo
> Borislav Petkov (2):
> tools/: Convert to new topic libraries
> perf: Move fs.* to lib/api/fs/
>
> tools/Makefile | 12 ++++----
> tools/lib/{lk => api}/Makefile | 8 ++++--
> tools/lib/{lk => api/fs}/debugfs.c | 0
> tools/lib/{lk => api/fs}/debugfs.h | 6 ++--
> tools/{perf/util => lib/api/fs}/fs.c | 11 ++++++--
> .../util/include/linux/magic.h => lib/api/fs/fs.h} | 12 ++++----
> tools/perf/Makefile.perf | 33 ++++++++++------------
> tools/perf/builtin-kvm.c | 2 +-
> tools/perf/builtin-probe.c | 2 +-
> tools/perf/perf.c | 2 +-
> tools/perf/tests/parse-events.c | 4 +--
> tools/perf/util/cpumap.c | 2 +-
> tools/perf/util/evlist.c | 2 +-
> tools/perf/util/evsel.c | 2 +-
> tools/perf/util/fs.h | 7 -----
> tools/perf/util/parse-events.c | 2 +-
> tools/perf/util/pmu.c | 2 +-
> tools/perf/util/probe-event.c | 2 +-
> tools/perf/util/python-ext-sources | 2 +-
> tools/perf/util/record.c | 2 +-
> tools/perf/util/setup.py | 4 +--
> tools/perf/util/trace-event-info.c | 2 +-
> tools/perf/util/util.h | 2 +-
> tools/vm/Makefile | 14 ++++-----
> tools/vm/page-types.c | 2 +-
> 25 files changed, 67 insertions(+), 72 deletions(-)
> rename tools/lib/{lk => api}/Makefile (85%)
> rename tools/lib/{lk => api/fs}/debugfs.c (100%)
> rename tools/lib/{lk => api/fs}/debugfs.h (86%)
> rename tools/{perf/util => lib/api/fs}/fs.c (91%)
> rename tools/{perf/util/include/linux/magic.h => lib/api/fs/fs.h} (50%)
> delete mode 100644 tools/perf/util/fs.h
>
> --
> 1.8.4
reply other threads:[~2013-12-05 17:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20131205174533.GE10333@ghostprotocols.net \
--to=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=dsahern@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.