From: "David S. Miller" <davem@davemloft.net>
To: pavel@ucw.cz
Cc: drepper@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: ntohs/ntohl and bitops
Date: Sat, 14 Jan 2006 17:46:59 -0800 (PST) [thread overview]
Message-ID: <20060114.174659.16358136.davem@davemloft.net> (raw)
In-Reply-To: <20060112010406.GA2367@ucw.cz>
From: Pavel Machek <pavel@ucw.cz>
Date: Thu, 12 Jan 2006 01:04:06 +0000
> Could you possibly
> #define IP_OFFSET htons(1234)
> ?
>
> Noone should need it in native endianity, no?
That's definitely going to be error prone.
And I bet the BSD headers define it in cpu endainness
as well.
prev parent reply other threads:[~2006-01-15 1:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-10 22:02 ntohs/ntohl and bitops Ulrich Drepper
2006-01-11 8:00 ` David S. Miller
2006-01-11 8:13 ` Arjan van de Ven
2006-01-11 8:36 ` David S. Miller
2006-01-11 8:36 ` Ulrich Drepper
2006-01-11 8:44 ` David S. Miller
2006-01-11 9:48 ` Jakub Jelinek
2006-01-11 18:35 ` Jan Engelhardt
2006-01-11 18:45 ` Ulrich Drepper
2006-01-11 20:19 ` David S. Miller
2006-01-12 1:04 ` Pavel Machek
2006-01-14 9:52 ` YOSHIFUJI Hideaki / 吉藤英明
2006-01-15 1:46 ` David S. 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=20060114.174659.16358136.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=drepper@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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).