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]
Message-Id: <20131120.150620.1185820553046155927.davem@davemloft.net>
Date:	Wed, 20 Nov 2013 15:06:20 -0500 (EST)
From:	David Miller <davem@...emloft.net>
To:	pmoore@...hat.com
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH] cipso: simplify cipso_v4_translate() when
 !CONFIG_NETLABEL

From: Paul Moore <pmoore@...hat.com>
Date: Wed, 20 Nov 2013 14:59:33 -0500

> On Wednesday, November 20, 2013 02:55:11 PM David Miller wrote:
>> 1) This is a cleanup, and therefore not suitable for submission right now
>>    because the net-next tree is closed.
> 
> I wasn't expecting it to go into the current merge window, I was just sending 
> it out now so you'd have it for when things started moving again.  Think of it 
> as spreading the pain out a bit.

When the merge window opens, I make an announcement here on the list
politely asking pople to defer net-next patch submissions until after
the merge window closes and I explicitly announce that net-next is
open again.

>> 2) A more suitable commit log message would have been "Don't needlessly
>>    recompute 'opt[opt_iter + 1]' as we already have it stored in tag_len".
>> 
>>    Then anyone who reads this commit message can say "yes, obviously this
>>    is a correct change and matches what the patch is doing"
> 
> Fair enough.  Do you want a resubmit with your wording once the merge window 
> closes?

... and I announce that net-next is open once more, yes.  Thank you.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ