1. 31 7月, 2012 1 次提交
    • A
      ext3: use memweight() · 10d47084
      Akinobu Mita 提交于
      Convert ext3_count_free() to use memweight() instead of table lookup
      based counting clear bits implementation.  This change only affects the
      code segments enabled by EXT3FS_DEBUG.
      
      Note that this memweight() call can't be replaced with a single
      bitmap_weight() call, although the pointer to the memory area is aligned
      to long-word boundary.  Because the size of the memory area may not be a
      multiple of BITS_PER_LONG, then it returns wrong value on big-endian
      architecture.
      
      This also includes the following changes.
      
      - Remove unnecessary map == NULL check in ext3_count_free() which
        always takes non-null pointer as the memory area.
      
      - Fix printk format warning that only reveals with EXT3FS_DEBUG.
      Signed-off-by: NAkinobu Mita <akinobu.mita@gmail.com>
      Acked-by: NJan Kara <jack@suse.cz>
      Cc: Andreas Dilger <adilger.kernel@dilger.ca>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      10d47084
  2. 01 4月, 2012 1 次提交
  3. 17 10月, 2007 1 次提交
  4. 27 9月, 2006 1 次提交
  5. 26 3月, 2006 1 次提交
  6. 11 1月, 2006 1 次提交
  7. 31 10月, 2005 1 次提交
    • B
      [PATCH] ext3: sparse fixes · 381be254
      Ben Dooks 提交于
      Fix warnings from sparse due to un-declared functions that should either
      have a header file or have been declared static
      
       fs/ext2/bitmap.c:14:15: warning: symbol 'ext2_count_free' was not declared. Should it be static?
       fs/ext2/namei.c:92:15: warning: symbol 'ext2_get_parent' was not declared. Should it be static?
       fs/ext3/bitmap.c:15:15: warning: symbol 'ext3_count_free' was not declared. Should it be static?
       fs/ext3/namei.c:1013:15: warning: symbol 'ext3_get_parent' was not declared. Should it be static?
       fs/ext3/xattr.c:214:1: warning: symbol 'ext3_xattr_block_get' was not declared. Should it be static?
       fs/ext3/xattr.c:358:1: warning: symbol 'ext3_xattr_block_list' was not declared. Should it be static?
       fs/ext3/xattr.c:630:1: warning: symbol 'ext3_xattr_block_find' was not declared. Should it be static?
       fs/ext3/xattr.c:863:1: warning: symbol 'ext3_xattr_ibody_find' was not declared. Should it be static?
      Signed-off-by: NBen Dooks <ben-linux@fluff.org>
      Signed-off-by: NAndrew Morton <akpm@osdl.org>
      Signed-off-by: NLinus Torvalds <torvalds@osdl.org>
      381be254
  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