From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Jiri Olsa <jolsa@kernel.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Ingo Molnar <mingo@kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Namhyung Kim <namhyung@kernel.org>,
David Ahern <dsahern@gmail.com>
Subject: Re: [PATCHv2 0/4] perf tools: Force fixdep to be built first
Date: Tue, 6 Dec 2016 13:10:40 -0300 [thread overview]
Message-ID: <20161206161040.GE2399@kernel.org> (raw)
In-Reply-To: <1481030331-31944-1-git-send-email-jolsa@kernel.org>
Em Tue, Dec 06, 2016 at 02:18:47PM +0100, Jiri Olsa escreveu:
> hi,
> changing Makefile.perf to force building fixdep before everything
> else, in order to avoid fixdep build races due to forgotten dependencies.
>
> And some build fixes that piled up around the fixdep change.
>
> Available also here:
> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> perf/fixes
>
> v2 changes:
> - keep the fixdep code more separated from the rest
> - added check-headers.sh script
> - added 2 extra fixes
Thanks, all tested and applied, passed the build-tests and container
based tests.
- Arnaldo
> thanks,
> jirka
>
>
> ---
> Jiri Olsa (4):
> perf tools: Move PERF-VERSION-FILE target into rules area
> perf tools: Force fixdep compilation at the start of the build
> perf tools: Move perf build related variables under non fixdep leg
> perf tools: Move headers check into bash script
>
> tools/perf/Makefile.perf | 162 +++++++++++++++++++++++++++++++------------------------------------------------------------------------
> tools/perf/check-headers.sh | 59 ++++++++++++++++++++++++++++++++++++++
> 2 files changed, 107 insertions(+), 114 deletions(-)
> create mode 100755 tools/perf/check-headers.sh
prev parent reply other threads:[~2016-12-06 16:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-06 13:18 [PATCHv2 0/4] perf tools: Force fixdep to be built first Jiri Olsa
2016-12-06 13:18 ` [PATCH 1/4] perf tools: Move PERF-VERSION-FILE target into rules area Jiri Olsa
2016-12-07 18:22 ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-12-06 13:18 ` [PATCH 2/4] perf tools: Force fixdep compilation at the start of the build Jiri Olsa
2016-12-07 18:23 ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-12-06 13:18 ` [PATCH 3/4] perf tools: Move perf build related variables under non fixdep leg Jiri Olsa
2016-12-07 18:23 ` [tip:perf/core] " tip-bot for Jiri Olsa
2016-12-06 13:18 ` [PATCH 4/4] perf tools: Move headers check into bash script Jiri Olsa
2016-12-20 19:19 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
2016-12-06 16:10 ` Arnaldo Carvalho de Melo [this message]
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=20161206161040.GE2399@kernel.org \
--to=acme@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=dsahern@gmail.com \
--cc=jolsa@kernel.org \
--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 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.