All of lore.kernel.org
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: __LITTLE_ENDIAN vs. __LITTLE_ENDIAN_BITFIELD
Date: Fri, 05 Oct 2007 13:27:57 -0500	[thread overview]
Message-ID: <4706822D.4070509@freescale.com> (raw)

What's the difference between __LITTLE_ENDIAN and __LITTLE_ENDIAN_BITFIELD? 
Can someone give me an example when __BIG_ENDIAN and __LITTLE_ENDIAN_BITFIELD 
would both be defined simultaneously?

-- 
Timur Tabi
Linux Kernel Developer @ Freescale

             reply	other threads:[~2007-10-05 18:28 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 18:27 Timur Tabi [this message]
2007-10-05 18:35 ` __LITTLE_ENDIAN vs. __LITTLE_ENDIAN_BITFIELD Jan Engelhardt
2007-10-05 19:35   ` Timur Tabi
2007-10-05 19:43     ` Jan Engelhardt
2007-10-05 19:47       ` Timur Tabi
2007-10-05 20:04         ` Andreas Schwab
2007-10-05 20:07           ` Timur Tabi
2007-10-05 20:34             ` linux-os (Dick Johnson)
2007-10-05 20:37               ` Timur Tabi
2007-10-05 23:27                 ` Benjamin Herrenschmidt
2007-10-05 21:17             ` Andreas Schwab
2007-10-05 21:06     ` Anton Altaparmakov
2007-10-05 21:10       ` Timur Tabi
2007-10-05 21:29         ` Andreas Schwab
2007-10-05 21:32           ` Timur Tabi
2007-10-05 23:17             ` Andreas Schwab
2007-10-09 17:46         ` Lennart Sorensen
2007-10-09 17:56           ` Timur Tabi
2007-10-09 18:34             ` Lennart Sorensen
2007-10-09 18:50             ` Krzysztof Halasa
2007-10-09 18:57               ` Timur Tabi
2007-10-09 19:37                 ` Krzysztof Halasa
2007-10-09 19:44                   ` Timur Tabi
2007-10-09 22:11                     ` Krzysztof Halasa
2007-10-09 19:11               ` Jeremy Fitzhardinge
2007-10-09 19:39                 ` Krzysztof Halasa
2007-10-09 21:40                   ` Jeremy Fitzhardinge
2007-10-09 22:34                     ` Krzysztof Halasa
2007-10-10 12:05                       ` linux-os (Dick Johnson)

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=4706822D.4070509@freescale.com \
    --to=timur@freescale.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.