netdev - Re: net-2.6.24 GIT state

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: <20070809.182719.99676246.davem@davemloft.net>
Date:	Thu, 09 Aug 2007 18:27:19 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	ilpo.jarvinen@...sinki.fi
Cc:	netdev@...r.kernel.org
Subject: Re: net-2.6.24 GIT state

From: "Ilpo_Järvinen" <ilpo.jarvinen@...sinki.fi>
Date: Thu, 9 Aug 2007 17:40:07 +0300 (EEST)

> Next step:
> 
> http://www.cs.helsinki.fi/u/ijjarvin/tcp-rebase/after-reorder/
> 
> ...I put some effort to reorganization and there's the result, please 
> _don't_ take the new SACK block-validator yet as I haven't yet put it 
> under any testing (it's the only difference this reordering of patches 
> seems to have introduced :-)). The first five commits touch left_out (4 
> latest fix bug and "flaws" I made in the first commit), I could combine 
> them into a single one if you want to.

I applied everything up until the SACK validator to net-2.6.24

Thanks for doing all of this merging work, I very much appreciate
it.

> ...Notice that part of the next step includes work that hasn't yet been 
> posted to netdev at all (was from my not yet submitted wip portion of 
> it). Would you prefer me to post them using the usual procedure?

Everything I hit today which had not been posted before was trivial
fix or a reasonable small cleanup.

Why don't you just post the patches to the list one-by-one from
now on so we can review them in parallel with merging into
net-2.6.24?

Thanks again Ilpo!
-
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