From: David Miller <davem@davemloft.net>
To: raj@tardy.usa.hp.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] doc: make the description of how tcp_ecn works more explicit and clear
Date: Thu, 29 Nov 2012 13:16:27 -0500 (EST) [thread overview]
Message-ID: <20121129.131627.987805831377793894.davem@davemloft.net> (raw)
In-Reply-To: <20121128195310.C438D2900459@tardy>
From: raj@tardy.usa.hp.com (Rick Jones)
Date: Wed, 28 Nov 2012 11:53:10 -0800 (PST)
> From: Rick Jones <rick.jones2@hp.com>
>
> Make the description of how tcp_ecn works a bit more explicit and clear.
>
> Signed-off-by: Rick Jones <rick.jones2@hp.com>
Applied, thanks Rick.
I think we should change the default to one, to be honest. I thought
that's what we were doing by now...
'2' made sense 10 years ago, but it doesn't really today.
next prev parent reply other threads:[~2012-11-29 18:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-28 19:53 [PATCH net-next] doc: make the description of how tcp_ecn works more explicit and clear Rick Jones
2012-11-29 18:16 ` David Miller [this message]
2012-11-29 18:42 ` Eric Dumazet
2012-11-29 18:58 ` Rick Jones
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=20121129.131627.987805831377793894.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).