From: Ingo Molnar <mingo@kernel.org>
To: hpa@zytor.com, paulus@samba.org, linux-kernel@vger.kernel.org,
acme@redhat.com, a.p.zijlstra@chello.nl, jolsa@redhat.com,
fweisbec@gmail.com, tglx@linutronix.de,
cjashfor@linux.vnet.ibm.com, mingo@elte.hu
Cc: linux-tip-commits@vger.kernel.org
Subject: Re: [tip:perf/core] perf tools: Fix parsers' rules to dependencies
Date: Sat, 14 Apr 2012 13:41:29 +0200 [thread overview]
Message-ID: <20120414114129.GF24688@gmail.com> (raw)
In-Reply-To: <tip-024e6c9747bb274c9d744ad52a987a0ebec528a6@git.kernel.org>
* tip-bot for Jiri Olsa <jolsa@redhat.com> wrote:
> Commit-ID: 024e6c9747bb274c9d744ad52a987a0ebec528a6
> Gitweb: http://git.kernel.org/tip/024e6c9747bb274c9d744ad52a987a0ebec528a6
> Author: Jiri Olsa <jolsa@redhat.com>
> AuthorDate: Wed, 11 Apr 2012 12:39:51 +0200
> Committer: Arnaldo Carvalho de Melo <acme@redhat.com>
> CommitDate: Wed, 11 Apr 2012 16:57:09 -0300
>
> perf tools: Fix parsers' rules to dependencies
>
> Currently the parsers objects (bison/flex related) are each time perf
> is built. No matter the generated files are already in place, the
> parser generation is executed every time.
>
> Changing the rules to have proper flex/bison objects generation
> dependencies.
>
> The parsers code is not rebuilt until the flex/bison source files
> are touched. Also when flex/bison source is changed, only dependent
> objects are rebuilt.
Hm, can I cherry-pick this over into perf/urgent? I see no good
reason why we should leave the v3.4 version half-broken.
Thanks,
Ingo
next prev parent reply other threads:[~2012-04-14 11:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 10:39 [PATCH] perf, tool: " Jiri Olsa
2012-04-13 18:18 ` [tip:perf/core] perf tools: " tip-bot for Jiri Olsa
2012-04-14 11:41 ` Ingo Molnar [this message]
2012-04-14 16:30 ` Arnaldo Carvalho de Melo
2012-04-15 8:36 ` [tip:perf/urgent] " tip-bot for Jiri Olsa
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=20120414114129.GF24688@gmail.com \
--to=mingo@kernel.org \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=cjashfor@linux.vnet.ibm.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
/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