From: "Randy.Dunlap" <rddunlap@osdl.org>
To: "YOSHIFUJI Hideaki / _$B5HF#1QL@" <yoshfuji@linux-ipv6.org>
Cc: davem@redhat.com, yoshfuji@linux-ipv6.org, netdev@oss.sgi.com
Subject: Re: [PATCH] IPV4: spelling correction
Date: Tue, 10 Feb 2004 10:30:50 -0800 [thread overview]
Message-ID: <20040210103050.63643c9a.rddunlap@osdl.org> (raw)
In-Reply-To: <20040211.032831.67897970.yoshfuji@linux-ipv6.org>
On Wed, 11 Feb 2004 03:28:31 +0900 (JST) YOSHIFUJI Hideaki / _$B5HF#1QL@ <yoshfuji@linux-ipv6.org> wrote:
a few comments (beginning with "**").
| D: spelling correction for net/ipv4
|
| ===== net/ipv4/tcp_input.c 1.49 vs edited =====
| --- 1.49/net/ipv4/tcp_input.c Mon Feb 2 04:22:45 2004
| +++ edited/net/ipv4/tcp_input.c Wed Feb 11 03:10:02 2004
| @@ -392,7 +392,7 @@
| if (tp->ack.ato > tp->rto)
| tp->ack.ato = tp->rto;
| } else if (m > tp->rto) {
| - /* Too long gap. Apparently sender falled to
| + /* Too long gap. Apparently sender fellen to
** failed
| * restart window, so that we send ACKs quickly.
| */
| tcp_incr_quickack(tp);
| @@ -431,7 +431,7 @@
| *
| * Funny. This algorithm seems to be very broken.
| * These formulae increase RTO, when it should be decreased, increase
| - * too slowly, when it should be incresed fastly, decrease too fastly
| + * too slowly, when it should be increased fastly, decrease too fastly
** s/fastly/quickly/ or s/fastly/fast/
| * etc. I guess in BSD RTO takes ONE value, so that it is absolutely
| * does not matter how to _calculate_ it. Seems, it was trap
| * that VJ failed to avoid. 8)
| @@ -493,14 +493,14 @@
| tp->rto = (tp->srtt >> 3) + tp->rttvar;
|
| /* 2. Fixups made earlier cannot be right.
| * If we do not estimate RTO correctly without them,
| * all the algo is pure shit and should be replaced
| - * with correct one. It is exaclty, which we pretend to do.
| + * with correct one. It is exactly, which we pretend to do.
** ^ what (delete comma)
| */
| }
|
| --
| Hideaki YOSHIFUJI @ USAGI Project <yoshfuji@linux-ipv6.org>
| GPG FP: 9022 65EB 1ECF 3AD1 0BDF 80D8 4807 F894 E062 0EEA
--
~Randy
next prev parent reply other threads:[~2004-02-10 18:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 18:28 [PATCH] IPV4: spelling correction YOSHIFUJI Hideaki / 吉藤英明
2004-02-10 18:30 ` Randy.Dunlap [this message]
2004-02-10 18:33 ` YOSHIFUJI Hideaki / 吉藤英明
2004-02-10 18:44 ` Nivedita Singhvi
2004-02-10 18:51 ` David S. Miller
2004-02-10 19:03 ` YOSHIFUJI Hideaki / 吉藤英明
2004-02-11 12:07 ` Arnaldo Carvalho de Melo
2004-02-11 13:41 ` jamal
2004-02-11 16:38 ` Nivedita Singhvi
2004-02-10 18:48 ` [PATCH] IPV4: spelling correction (Take 3) YOSHIFUJI Hideaki / 吉藤英明
2004-02-10 18:34 ` [PATCH] IPV4: spelling correction Chris Wright
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=20040210103050.63643c9a.rddunlap@osdl.org \
--to=rddunlap@osdl.org \
--cc=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=yoshfuji@linux-ipv6.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).