linux-kernel - Re: [PATCH v2] 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: <50F72706.5090900@oracle.com>
Date:	Wed, 16 Jan 2013 17:17:42 -0500
From:	Sasha Levin <sasha.levin@...cle.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
CC:	Peter Senna Tschudin <peter.senna@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] hlist: drop the node parameter from iterators

On 01/16/2013 05:04 PM, Linus Torvalds wrote:
> On Wed, Jan 16, 2013 at 1:58 PM, Sasha Levin <sasha.levin@...cle.com> wrote:
>>
>> I guess that if you agree that it should go in once it had some more
>> testing, it can go into linux-next and sit there for the next couple
>> of weeks until the next merge window opens.
> 
> So linux-next gets compile testing and warns about conflicts. But
> almost nobody really runs the end result.

I do :)

I also know that people run ltp tests on top of those builds, so while
it's not as good as actually working with it, it's also not
insignificant.

> Now, *hopefully* the compile problems and conflicts are the major
> issue, but at the same time, I worry about some actual subtle semantic
> breakage. I'm not sure how it would happen, but it's a big patch..
> 
>> What would be the best way to do that though? see if akpm would take
>> it into his tree?
> 
> That would help. As would just linux-next. As would just after the
> next merge window closes, if you can send it almost immediately *and*
> have the "at least the patch has been around for a long time with no
> *known* breakage" note. Because at some point, I guess we can't do
> much more than that.

Alrighty, right after merge window it is. The -rc4 period is what you
told me the last time I sent this patch, so I went with that this time.

I'll resend this patch to Andrew in hopes that he'll be okay with
having it in his tree until the next window.

Thanks!

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