1. 05 3月, 2008 1 次提交
    • J
      CRIS: Import string.c (memcpy) from newlib: fixes compile error with gcc 4 · 9fe3fd03
      Jesper Nilsson 提交于
      Adrian Bunk reported another compile error with a SVN head GCC:
      
      ...
        CC      arch/cris/arch-v10/lib/string.o
      /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/cris/arch-v10/lib/string.c:138:
      error: lvalue required as increment operand
      /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/cris/arch-v10/lib/string.c:138:
      error: lvalue required as increment operand
      /home/bunk/linux/kernel-2.6/git/linux-2.6/arch/cris/arch-v10/lib/string.c:139:
      error: lvalue required as increment operand
      ...
      
      This is due to the use of the construct:
      
      	*((long*)dst)++ = lc;
      
      Which isn't legal since casts don't return an lvalue.
      
      The solution is to import the implementation from newlib,
      which is continually autotested together with GCC mainline,
      and uses the construct:
      
      	*(long *) dst = lc; dst += 4;
      
      Since this is an import of a file from newlib, I'm not touching
      the formatting or correcting any checkpatch errors.
      
      As for the earlier fix for memset.c, even if the two files for
      CRIS v10 and CRIS v32 are identical at the moment, it might
      be possible to tweak the CRIS v32 version.
      Thus, I'm not yet folding them into the same file, at least not
      until we've done some research on it.
      Signed-off-by: NJesper Nilsson <jesper.nilsson@axis.com>
      Cc: Mikael Starvik <starvik@axis.com>
      Cc: Adrian Bunk <bunk@stusta.de>
      Signed-off-by: NAndrew Morton <akpm@linux-foundation.org>
      Signed-off-by: NLinus Torvalds <torvalds@linux-foundation.org>
      9fe3fd03
  2. 20 10月, 2007 1 次提交
  3. 28 7月, 2005 1 次提交
  4. 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