linux-kernel - Re: [GIT PULL] tracing: Updates for 4.4

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:	Sat, 7 Nov 2015 09:09:27 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Steven Rostedt <rostedt@...dmis.org>,
	LKML <linux-kernel@...r.kernel.org>,
	Ingo Molnar <mingo@...nel.org>,
	Sergey Senozhatsky <sergey.senozhatsky.work@...il.com>
Subject: Re: [GIT PULL] tracing: Updates for 4.4

Hi Linus,

On Fri, 6 Nov 2015 13:37:48 -0800 Linus Torvalds <torvalds@...ux-foundation.org> wrote:
>
> So where did this all fail? Nobody ever looked at the warnings from
> linux-next? Or it wasn't even in linux-next long enough to really ever
> trigger?

This was reported against linux-next on Nov 2 by Sergey Senozhatsky who
supplied a fix patch that I then used as the merge conflict resolution
from Nov 3 onward (which everyone involved knew about) ...

I also noticed it, but was a bit under the weather and tired to do
anything about it immediately.

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au
--
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/