netdev - Re: [PATCH 2/2][TCP] YeAH-TCP: limited slow start exported function

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <8dd26e70702220808s49a11c03p83da65c164808f52@mail.gmail.com>
Date:	Thu, 22 Feb 2007 17:08:37 +0100
From:	"Angelo P. Castellani" <angelo.castellani@...il.com>
To:	"David Miller" <davem@...emloft.net>
Cc:	netdev@...r.kernel.org, andrea.baiocchi@...roma1.it,
	francesco@....infocom.uniroma1.it
Subject: Re: [PATCH 2/2][TCP] YeAH-TCP: limited slow start exported function

Ok, I've missed this bit in the submitting patches documentation..
however sorry for that.

2007/2/22, David Miller <davem@...emloft.net>:
> Please never submit patches like this, submit the infrastructure
> FIRST, then submit the stuff that uses it.  When a sequence of patches
> is applied, in sequence, the tree should build properly (even with all
> available new options enabled) at each step along the way.
>
> Otherwise we have the situation we have now, in that YeaH is in my
> tree but doesn't build successfully.
>
> What I'm going to do to "fix" this, is yank YeaH implementation out
> of my tree, add this second patch first, then add the YeaH patch
> back.
>
> Please never do this again.
>
-
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