From: David Miller <davem@davemloft.net>
To: raj@tardy.usa.hp.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] doc: Tighten-up and clarify description of tcp_fin_timeout
Date: Mon, 10 Dec 2012 17:14:44 -0500 (EST) [thread overview]
Message-ID: <20121210.171444.1204644598241869819.davem@davemloft.net> (raw)
In-Reply-To: <20121210213300.9D6BB29003EA@tardy>
From: raj@tardy.usa.hp.com (Rick Jones)
Date: Mon, 10 Dec 2012 13:33:00 -0800 (PST)
> From: Rick Jones <rick.jones2@hp.com>
>
> The description for tcp_fin_timeout should be tigher and more clear.
>
> In addition to being tighter, we should make the spelling of the
> state name consistent with what utilities report, remove the now
> dated reference to 2.2 and put the default in the consistent place.
>
> Signed-off-by: Rick Jones <rick.jones2@hp.com>
Applied, thanks Rick.
prev parent reply other threads:[~2012-12-10 22:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-10 21:33 [PATCH net-next] doc: Tighten-up and clarify description of tcp_fin_timeout Rick Jones
2012-12-10 22:14 ` 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=20121210.171444.1204644598241869819.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=raj@tardy.usa.hp.com \
/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).