From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Ingo Molnar <mingo@kernel.org>
Cc: linux-kernel@vger.kernel.org,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Adrian Hunter <adrian.hunter@intel.com>,
Borislav Petkov <bp@suse.de>, David Ahern <dsahern@gmail.com>,
Frederic Weisbecker <fweisbec@gmail.com>,
Jiri Olsa <jolsa@redhat.com>, Namhyung Kim <namhyung@kernel.org>,
Stephane Eranian <eranian@google.com>,
Arnaldo Carvalho de Melo <acme@redhat.com>
Subject: [GIT PULL 0/2] Two extra perf/urgent fixes
Date: Thu, 9 Jul 2015 18:14:19 -0300 [thread overview]
Message-ID: <1436476461-8020-1-git-send-email-acme@kernel.org> (raw)
Hi Ingo,
Please consider pulling, a fallout from removing linux/export.h
when copying rbtree.c and removing kernel specific stuff (EXPORT_SYMBOL),
this is on top of my previous perf-urgent-for-mingo pull req.
- Arnaldo
The following changes since commit 08ae217b8d44986062fe3648c5bb83816d5bc00f:
perf thread_map: Fix the sizeof() calculation for map entries (2015-07-09 12:28:53 -0300)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/acme/linux.git tags/perf-urgent-for-mingo-2
for you to fetch changes up to 0aefc3590afcc9ecbe173fc01fccbda0869d2f0a:
tools: Copy lib/hweight.c from the kernel sources (2015-07-09 16:29:56 -0300)
----------------------------------------------------------------
perf/urgent fixes:
These are only noticed when doing a detached tarball, i.e. when one does:
make perf-perf-tar-src-pkg
to create a perf-4.2.0-rc1.tar file and then try to build the contents of this
tarball:
- The python binding also has a MANIFEST like file where we list the files that
need to be built and linked to form the resulting python shared object module
file. And it has an entry for rbtree.c that still pointed to the one in the
kernel sources, fix it by also removing one level of indirection so that it
uses the tools/lib/rbtree.c copy. (Arnaldo Carvalho de Melo)
- For the same reasons as for rbtree.c, copy the kernel lib/hweight.c file to
tools/lib/, sanitizing it in the process to remove kernel specific stuff like
EXPORT_SYMBOL() lines and the linux/export.h include reference, as that file
doesn't exist anymore in tools/include/linux. (Arnaldo Carvalho de Melo)
Signed-off-by: Arnaldo Carvalho de Melo <acme@redhat.com>
----------------------------------------------------------------
Arnaldo Carvalho de Melo (2):
perf tools: Fix the detached tarball wrt rbtree copy
tools: Copy lib/hweight.c from the kernel sources
tools/lib/hweight.c | 62 ++++++++++++++++++++++++++++++++++++++
tools/perf/MANIFEST | 2 +-
tools/perf/util/Build | 2 +-
tools/perf/util/python-ext-sources | 4 +--
4 files changed, 66 insertions(+), 4 deletions(-)
create mode 100644 tools/lib/hweight.c
next reply other threads:[~2015-07-09 21:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-09 21:14 Arnaldo Carvalho de Melo [this message]
2015-07-09 21:14 ` [PATCH 1/2] perf tools: Fix the detached tarball wrt rbtree copy Arnaldo Carvalho de Melo
2015-07-09 21:14 ` [PATCH 2/2] tools: Copy lib/hweight.c from the kernel sources Arnaldo Carvalho de Melo
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=1436476461-8020-1-git-send-email-acme@kernel.org \
--to=acme@kernel.org \
--cc=acme@redhat.com \
--cc=adrian.hunter@intel.com \
--cc=bp@suse.de \
--cc=dsahern@gmail.com \
--cc=eranian@google.com \
--cc=fweisbec@gmail.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=namhyung@kernel.org \
/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
Powered by JetHome