From: David Miller <davem@davemloft.net>
To: apetlund@simula.no
Cc: johunt@akamai.com, kuznet@ms2.inr.ac.ru, jmorris@namei.org,
kaber@trash.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, juhlenko@akamai.com
Subject: Re: [PATCH] net: Add getsockopt support for TCP thin-streams
Date: Mon, 02 Aug 2010 17:25:38 -0700 (PDT) [thread overview]
Message-ID: <20100802.172538.220060944.davem@davemloft.net> (raw)
In-Reply-To: <4C56B018.8030309@simula.no>
From: Andreas Petlund <apetlund@simula.no>
Date: Mon, 02 Aug 2010 13:46:32 +0200
> On 07/31/2010 01:49 AM, Josh Hunt wrote:
>> Initial TCP thin-stream commit did not add getsockopt support for the new
>> socket options: TCP_THIN_LINEAR_TIMEOUTS and TCP_THIN_DUPACK. This adds support
>> for them.
>>
>> Signed-off-by: Josh Hunt <johunt@akamai.com>
...
> Tested-by: Andreas Petlund <apetlund@simula.no>
> Acked-by: Andreas Petlund <apetlund@simula.no>
Applied, thanks.
prev parent reply other threads:[~2010-08-03 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-30 23:49 [PATCH] net: Add getsockopt support for TCP thin-streams Josh Hunt
2010-08-02 11:46 ` Andreas Petlund
2010-08-03 0:25 ` David Miller [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100802.172538.220060944.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=apetlund@simula.no \
--cc=jmorris@namei.org \
--cc=johunt@akamai.com \
--cc=juhlenko@akamai.com \
--cc=kaber@trash.net \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).