linux-kernel - Re: linux-next: Tree for Nov 14

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:	Wed, 14 Nov 2012 18:03:08 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	<linux-next@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
	Linus <torvalds@...ux-foundation.org>,
	Ingo Molnar <mingo@...e.hu>, Hugh Dickins <hughd@...gle.com>
Subject: Re: linux-next: Tree for Nov 14

On Wed, 14 Nov 2012 17:55:28 +1100 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
>
> On Tue, 13 Nov 2012 21:37:42 -0800 Andrew Morton <akpm@...ux-foundation.org> wrote:
> >
> > It would help if the old sched/numa code wasn't in -next while you're
> > away.  That would give me a clean run at 3.7 and will make it easier
> > for others to integrate and test the four(!) different
> > autoschednumacore implementations on top of linux-next.
> > 
> > Pretty please?
> 
> So, your understanding is that the "old sched/numa code" won't (and
> shouldn't) be merged into Linus' tree (for v3.7, or ever)?
> 
> In that case, what I can do is give you a tree that is the same as
> akpm-base but with one of the merges in the tip tree reverted (and, in
> fact, I could push that into akpm-base to make things easier for you).
> I guess that would be the merge of the numa/core branch which would
> result in the following commits being reverted:

Ok, ignore all this :-(

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

Content of type "application/pgp-signature" skipped