public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederik Deweerdt <deweerdt@free.fr>
To: Allexio Ju <allexio.ju@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: trivial question regarding byte ordering
Date: Fri, 23 Feb 2007 15:24:11 +0000	[thread overview]
Message-ID: <20070223152411.GA31486@slug> (raw)
In-Reply-To: <a02278b00702230718i74df1d63g954bd7ac83298696@mail.gmail.com>

On Fri, Feb 23, 2007 at 07:18:13AM -0800, Allexio Ju wrote:
> Is there a API (or macro) that checks CPU endianness and does byte
> ordering conversion on given data (32-bit) if endianness is
> big-endian?
including include/asm/byteorder.h will define the needed
cpu_to_{b,l}e{16,32,64} and {b,l}e{16,32,64}_to_cpu macros.

Regards,
Frederik

  parent reply	other threads:[~2007-02-23 15:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 15:18 trivial question regarding byte ordering Allexio Ju
2007-02-23 15:23 ` Robert P. J. Day
2007-02-23 18:00   ` Allexio Ju
2007-02-23 15:24 ` Frederik Deweerdt [this message]
2007-02-23 18:01   ` Allexio Ju

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=20070223152411.GA31486@slug \
    --to=deweerdt@free.fr \
    --cc=allexio.ju@gmail.com \
    --cc=linux-kernel@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