1. 05 3月, 2016 1 次提交
  2. 08 8月, 2015 2 次提交
    • L
      powerpc: add support for csum_add() · 501c8de7
      LEROY Christophe 提交于
      The C version of csum_add() as defined in include/net/checksum.h gives
      the following assembly in ppc32:
             0:       7c 04 1a 14     add     r0,r4,r3
             4:       7c 64 00 10     subfc   r3,r4,r0
             8:       7c 63 19 10     subfe   r3,r3,r3
             c:       7c 63 00 50     subf    r3,r3,r0
      and the following in ppc64:
         0xc000000000001af8 <+0>:	add     r3,r3,r4
         0xc000000000001afc <+4>:	cmplw   cr7,r3,r4
         0xc000000000001b00 <+8>:	mfcr    r4
         0xc000000000001b04 <+12>:	rlwinm  r4,r4,29,31,31
         0xc000000000001b08 <+16>:	add     r3,r4,r3
         0xc000000000001b0c <+20>:	clrldi  r3,r3,32
         0xc000000000001b10 <+24>:	blr
      
      include/net/checksum.h also offers the possibility to define an arch
      specific function.  This patch provides a specific csum_add() inline
      function.
      Signed-off-by: NChristophe Leroy <christophe.leroy@c-s.fr>
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      501c8de7
    • L
      powerpc: put csum_tcpudp_magic inline · 92c985f1
      LEROY Christophe 提交于
      csum_tcpudp_magic() is only a few instructions, and does modify
      really few registers. So it is not worth having it as a separate
      function and suffer function branching and saving of volatile
      registers.
      
      This patch makes it inline by use of the already existing
      csum_tcpudp_nofold() function.
      Signed-off-by: NChristophe Leroy <christophe.leroy@c-s.fr>
      Signed-off-by: NScott Wood <scottwood@freescale.com>
      92c985f1
  3. 11 10月, 2013 1 次提交
  4. 02 9月, 2010 2 次提交
  5. 04 8月, 2008 1 次提交
  6. 03 12月, 2006 1 次提交
  7. 09 1月, 2006 1 次提交
  8. 26 10月, 2005 1 次提交
  9. 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