summaryrefslogtreecommitdiffstats
path: root/include/linux/byteorder/big_endian.h
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@linux-foundation.org>2010-05-26 08:30:15 -0700
committerLinus Torvalds <torvalds@linux-foundation.org>2010-05-26 08:30:15 -0700
commit13da9e200fe4740b02cd51e07ab454627e228920 (patch)
treee65f37a59c2a0e1695d5094a8f5509839e1d30cc /include/linux/byteorder/big_endian.h
parent4e89e8f61bcdff82a7b63b80ed83a6725028d61b (diff)
downloadop-kernel-dev-13da9e200fe4740b02cd51e07ab454627e228920.zip
op-kernel-dev-13da9e200fe4740b02cd51e07ab454627e228920.tar.gz
Revert "endian: #define __BYTE_ORDER"
This reverts commit b3b77c8caef1750ebeea1054e39e358550ea9f55, which was also totally broken (see commit 0d2daf5cc858 that reverted the crc32 version of it). As reported by Stephen Rothwell, it causes problems on big-endian machines: > In file included from fs/jfs/jfs_types.h:33, > from fs/jfs/jfs_incore.h:26, > from fs/jfs/file.c:22: > fs/jfs/endian24.h:36:101: warning: "__LITTLE_ENDIAN" is not defined The kernel has never had that crazy "__BYTE_ORDER == __LITTLE_ENDIAN" model. It's not how we do things, and it isn't how we _should_ do things. So don't go there. Requested-by: Stephen Rothwell <sfr@canb.auug.org.au> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Diffstat (limited to 'include/linux/byteorder/big_endian.h')
-rw-r--r--include/linux/byteorder/big_endian.h3
1 files changed, 0 insertions, 3 deletions
diff --git a/include/linux/byteorder/big_endian.h b/include/linux/byteorder/big_endian.h
index d53a67d..3c80fd7 100644
--- a/include/linux/byteorder/big_endian.h
+++ b/include/linux/byteorder/big_endian.h
@@ -7,9 +7,6 @@
#ifndef __BIG_ENDIAN_BITFIELD
#define __BIG_ENDIAN_BITFIELD
#endif
-#ifndef __BYTE_ORDER
-#define __BYTE_ORDER __BIG_ENDIAN
-#endif
#include <linux/types.h>
#include <linux/swab.h>
OpenPOWER on IntegriCloud