linux-kernel - Re: [GIT PULL] perf changes for v4.8

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]

Date:	Mon, 25 Jul 2016 17:35:36 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Arnaldo Carvalho de Melo <acme@...radead.org>,
	Jiri Olsa <jolsa@...hat.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] perf changes for v4.8


* Ingo Molnar <mingo@...nel.org> wrote:

> 
> * Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> 
> > Hi Ingo,
> > 
> > On Mon, 25 Jul 2016 10:28:38 +0200 Ingo Molnar <mingo@...nel.org> wrote:
> > >
> > >       tools: Copy the bitops files accessed from the kernel and check for drift
> > 
> > I think this has some needs some fixes for build breakage in linux-next ...
> 
> Only if combined with a single pending change from the luto-next tree, right?

... which commits come through the x86 tree, so there's no way for Linus to be 
exposed to that, right?

That is why I sent this without mentioning the conflict. Is there any other 
complication that I missed?

Thanks,

	Ingo