1. 13 10月, 2012 1 次提交
  2. 26 5月, 2010 1 次提交
    • L
      Revert "endian: #define __BYTE_ORDER" · 13da9e20
      Linus Torvalds 提交于
      This reverts commit b3b77c8c, which was
      also totally broken (see commit 0d2daf5c 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: NStephen Rothwell <sfr@canb.auug.org.au>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      13da9e20
  3. 25 5月, 2010 1 次提交
  4. 07 1月, 2009 1 次提交
    • H
      byteorder: only use linux/swab.h · 991c0e6d
      Harvey Harrison 提交于
      The first step to make swab.h a regular header that will
      include an asm/swab.h with arch overrides.
      
      Avoid the gratuitous differences introduced in the new
      linux/swab.h by naming the ___constant_swabXX bits and
      __fswabXX bits exactly as found in the old implementation
      in byteorder/swab[b].h
      
      Use this new swab.h in byteorder/[big|little]_endian.h and
      remove the two old swab headers.
      
      Although the inclusion of asm/byteorder.h looks strange in
      linux/swab.h, this will allow each arch to move the actual
      arch overrides for the swab bits in an asm file and then
      the includes can be cleaned up without requiring a flag day
      for all arches at once.
      
      Keep providing __fswabXX in case some userspace was using them
      directly, but the revised __swabXX should be used instead in
      any new code and will always do constant folding not dependent
      on the optimization level, which means the __constant versions
      can be phased out in-kernel.
      
      Arches that use the old-style arch macros will lose their
      optimized versions until they move to the new style, but at
      least they will still compile.  Many arches have already moved
      and the patches to move the remaining arches are trivial.
      Signed-off-by: NHarvey Harrison <harvey.harrison@gmail.com>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      991c0e6d
  5. 20 10月, 2008 1 次提交
  6. 26 7月, 2008 1 次提交
  7. 30 4月, 2008 1 次提交
  8. 17 4月, 2005 1 次提交
    • L
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds 提交于
      Initial git repository build. I'm not bothering with the full history,
      even though we have it. We can create a separate "historical" git
      archive of that later if we want to, and in the meantime it's about
      3.2GB when imported into git - space that would just make the early
      git days unnecessarily complicated, when we don't have a lot of good
      infrastructure for it.
      
      Let it rip!
      1da177e4