linux-kernel - Re: [GIT PULL] locking tree changes for v3.16

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:	Thu, 5 Jun 2014 11:24:37 +0200
From:	Ingo Molnar <mingo@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Davidlohr Bueso <davidlohr@...com>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org,
	"Paul E. McKenney" <paulmck@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: [GIT PULL] locking tree changes for v3.16


* Peter Zijlstra <peterz@...radead.org> wrote:

> On Thu, Jun 05, 2014 at 10:17:42AM +0200, Ingo Molnar wrote:
> > 
> > Right now I'm somewhat 'missing' because I fell ill right when the 
> > merge window began :-/ But I merged all your pending bits shortly 
> > before the merge window started. During the merge window itself I 
> > try not to merge fresh patches.
> 
> Yeah, no problem that, it just shows we need to better arrange 
> things for when you're not available.
> 
> My/our quilt workflow works really good for me when you're there, 
> but its obviously somewhat broken without you. We just need to work 
> out a (better) fallback case.

Agreed.

> The timing was just somewhat unfortunate.

Yeah, and another part of the problem was that I reported the breakage 
in private which really made it harder for others to see why there's a 
delay.

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/