From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Miller Subject: Re: [PATCH net-next] remove an outdated reference to T/TCP Date: Tue, 06 Dec 2011 16:42:43 -0500 (EST) Message-ID: <20111206.164243.402402261622724566.davem@davemloft.net> References: <20111206200005.836D529006DD@tardy> <20111206.151920.696192671128392379.davem@davemloft.net> <4EDE8B8B.2000907@hp.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: netdev@vger.kernel.org To: rick.jones2@hp.com Return-path: Received: from shards.monkeyblade.net ([198.137.202.13]:34156 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752853Ab1LFVm6 (ORCPT ); Tue, 6 Dec 2011 16:42:58 -0500 In-Reply-To: <4EDE8B8B.2000907@hp.com> Sender: netdev-owner@vger.kernel.org List-ID: From: Rick Jones Date: Tue, 06 Dec 2011 13:39:23 -0800 > On 12/06/2011 12:19 PM, David Miller wrote: >> From: Rick Jones >> Date: Tue, 6 Dec 2011 12:00:05 -0800 (PST) >> >>> >>> Remove a particularly out of date bit of comment referring to T/TCP. >>> >>> Signed-off-by: Rick Jones >> >> I think it should stay because it discusses the potential bad side >> effects of queueing any data that might be in the SYN. > > How about just the sentence that mentioned T/TCP explicitly since > T/TCP is most definitely no longer starting to be used?-) The rest of > it can be discussed when/if TCP Fast Open arrives :) T/TCP gives the statement context, as in referencing something that might make us want to at least theoretically consider handling the data.