linux-kernel - Re: [PATCH 00/14] tools build: Move features framework into tools/build

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 for Android: free password hash cracker in your pocket

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

Date:	Wed, 4 Mar 2015 05:41:58 +0100
From:	Ingo Molnar <mingo@...nel.org>
To:	Jiri Olsa <jolsa@...nel.org>
Cc:	linux-kernel@...r.kernel.org,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>,
	David Ahern <david.ahern@...cle.com>,
	Namhyung Kim <namhyung@...nel.org>,
	Paul Mackerras <paulus@...ba.org>,
	Peter Zijlstra <peterz@...radead.org>
Subject: Re: [PATCH 00/14] tools build: Move features framework into
 tools/build


* Jiri Olsa <jolsa@...nel.org> wrote:

> hi,
> moving features detection framework from perf to 'tools/build'
> plus other minor fixes.
> 
> It's also available in:
> git://git.kernel.org/pub/scm/linux/kernel/git/jolsa/perf.git
> perf/build

So the series looks really good to me, and I also tested it, pulled it 
on top of tip:master, and feature detection still worked just as 
expected.

I noticed one detail:

> Jiri Olsa (14):
>       tools build: Remove Copyright from credits message

Please just leave the current credits in place, as these gents 
certainly have a copyright in the code as well, and since we pushed 
the original attribution upstream already, so we cannot (and don't 
want to) remove it. But yes, in general authors add their own 
copyrights.

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/