From: Neil Horman <nhorman@tuxdriver.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Andy Gospodarek <andy@greyhouse.net>, netdev@vger.kernel.org
Subject: Re: [PATCH net-next-2.6] net: add support for htonb and ntohb
Date: Thu, 1 Apr 2010 20:03:44 -0400 [thread overview]
Message-ID: <20100402000344.GB8930@hmsreliant.think-freely.org> (raw)
In-Reply-To: <1270154854.2192.3.camel@edumazet-laptop>
On Thu, Apr 01, 2010 at 10:47:34PM +0200, Eric Dumazet wrote:
> Le jeudi 01 avril 2010 à 16:32 -0400, Andy Gospodarek a écrit :
> > After my recent post to net-2.6 this week to accidentally run htons to a
> > u8, it is clear to me we _must_ add some infrastructure to make sure
> > single bytes are in the correct network and host order on big and little
> > endian systems. Today seemed like the perfect day to post this.
> >
> > This patch adds basic support for htonb and ntohb. Patches to add this
> > in the entire networking tree in _every_ case where a single byte is
> > accessed will be posted next week -- I'm almost done with them!
> >
> > Signed-off-by: Andy Gospodarek <andy@greyhouse.net>
> > ---
>
> Seems fine, thanks a lot Andy.
>
> Hmm, I notice this doesnt handle yet arches where a byte is 9 bits long.
>
> Do you have any plan, to finally support PDP-6/10 ?
>
definately, and while your at it, I could really use some conversion routines
for the more complex types just to save time. htonstr and ntohstr in particular
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2010-04-02 0:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 20:32 [PATCH net-next-2.6] net: add support for htonb and ntohb Andy Gospodarek
2010-04-01 20:47 ` Eric Dumazet
2010-04-02 0:03 ` Neil Horman [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=20100402000344.GB8930@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=andy@greyhouse.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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