From: "David S. Miller" <davem@davemloft.net>
To: Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp>
Cc: netdev@oss.sgi.com, usagi-core@linux-ipv6.org
Subject: Re: [PATCH]: fixed typo of reassembly.c
Date: Fri, 1 Oct 2004 15:19:23 -0700 [thread overview]
Message-ID: <20041001151923.261b42b3.davem@davemloft.net> (raw)
In-Reply-To: <200409301023.i8UANRGp002783@toshiba.co.jp>
On Thu, 30 Sep 2004 19:23:26 +0900 (JST)
Yasuyuki Kozakai <yasuyuki.kozakai@toshiba.co.jp> wrote:
> This patch fixes byte ordering. Please apply this.
It is textual fix only, do you realize this?
Both ntohs() and htons() perform the same transformation
on a 16-bit data item. It really does not matter which
one you actually use, in practice.
I will apply your patch anyways, I just wanted to be
clear that this does not actually fix any bug. :-)
THanks.
next prev parent reply other threads:[~2004-10-01 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-30 10:23 [PATCH]: fixed typo of reassembly.c Yasuyuki Kozakai
2004-10-01 22:19 ` David S. Miller [this message]
2004-10-02 5:02 ` Herbert Xu
2004-10-02 6:38 ` David S. Miller
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=20041001151923.261b42b3.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=netdev@oss.sgi.com \
--cc=usagi-core@linux-ipv6.org \
--cc=yasuyuki.kozakai@toshiba.co.jp \
/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).