linux-kernel - Re: [tip:perf/core] perf tools: Fix parsers' rules to dependencies

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20120414163009.GE22114@infradead.org>
Date:	Sat, 14 Apr 2012 13:30:09 -0300
From:	Arnaldo Carvalho de Melo <acme@...hat.com>
To:	Ingo Molnar <mingo@...nel.org>
Cc:	hpa@...or.com, paulus@...ba.org, linux-kernel@...r.kernel.org,
	a.p.zijlstra@...llo.nl, jolsa@...hat.com, fweisbec@...il.com,
	tglx@...utronix.de, cjashfor@...ux.vnet.ibm.com, mingo@...e.hu,
	linux-tip-commits@...r.kernel.org
Subject: Re: [tip:perf/core] perf tools: Fix parsers' rules to dependencies

Em Sat, Apr 14, 2012 at 01:41:29PM +0200, Ingo Molnar escreveu:
> 
> * tip-bot for Jiri Olsa <jolsa@...hat.com> wrote:
> 
> > Commit-ID:  024e6c9747bb274c9d744ad52a987a0ebec528a6
> > Gitweb:     http://git.kernel.org/tip/024e6c9747bb274c9d744ad52a987a0ebec528a6
> > Author:     Jiri Olsa <jolsa@...hat.com>
> > AuthorDate: Wed, 11 Apr 2012 12:39:51 +0200
> > Committer:  Arnaldo Carvalho de Melo <acme@...hat.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.

Feel free! Overcautious me, wanting to push just only strict bug fixes
there, this one I found just a minor annoyance, so left for perf/core.
 
> Thanks,
> 
> 	Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/