linux-kernel - Re: [RFC] hlist: drop the node parameter from iterators

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] [day] [month] [year] [list]

Message-ID: <CA+55aFyOX5qiakpoSBELCAbc3xkcxqf_-dcaxb40Gtrp7BXenw@mail.gmail.com>
Date:	Fri, 2 Nov 2012 13:39:43 -0700
From:	Linus Torvalds <torvalds@...ux-foundation.org>
To:	Sasha Levin <sasha.levin@...cle.com>
Cc:	paulmck@...ux.vnet.ibm.com, dipankar@...ibm.com, mingo@...nel.org,
	hpa@...or.com, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, peter.senna@...il.com
Subject: Re: [RFC] hlist: drop the node parameter from iterators

On Fri, Nov 2, 2012 at 1:33 PM, Sasha Levin <sasha.levin@...cle.com> wrote:
>
> Do you want the patch on top of your git head, or on top of -next?

So the thing is, there's no way I'm going to apply this kind of patch
anywhere *near* a merge window. With something like this, it needs to
get applied a few weeks after the merge window closes (when things
have calmed down) _and_ a few weeks before the next one opens (so that
we see the results in -next, and don't scramble for the next merge
window). IOW, around the -rc4 timeframe.

It sounds like it's not quite ready yet, which means that I'm not
comfy with it this round, and we'd better do this around 3.8-rc4 or so
(ie roughly this timeframe of the next release - I'll do 3.7-rc4
either today or tomorrow).

             Linus
--
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/