Skip to content
Snippets Groups Projects
  1. Jun 13, 2011
  2. Jun 06, 2011
  3. Dec 21, 2010
  4. Aug 25, 2010
  5. May 14, 2010
    • Joe Perches's avatar
      drivers/net: Remove unnecessary returns from void function()s · a4b77097
      Joe Perches authored
      
      This patch removes from drivers/net/ all the unnecessary
      return; statements that precede the last closing brace of
      void functions.
      
      It does not remove the returns that are immediately
      preceded by a label as gcc doesn't like that.
      
      It also does not remove null void functions with return.
      
      Done via:
      $ grep -rP --include=*.[ch] -l "return;\n}" net/ | \
        xargs perl -i -e 'local $/ ; while (<>) { s/\n[ \t\n]+return;\n}/\n}/g; print; }'
      
      with some cleanups by hand.
      
      Compile tested x86 allmodconfig only.
      
      Signed-off-by: default avatarJoe Perches <joe@perches.com>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      a4b77097
  6. Apr 07, 2010
    • Ben Hutchings's avatar
      3c503: Fix IRQ probing · b0cf4dfb
      Ben Hutchings authored
      The driver attempts to select an IRQ for the NIC automatically by
      testing which of the supported IRQs are available and then probing
      each available IRQ with probe_irq_{on,off}().  There are obvious race
      conditions here, besides which:
      1. The test for availability is done by passing a NULL handler, which
         now always returns -EINVAL, thus the device cannot be opened:
         <http://bugs.debian.org/566522
      
      >
      2. probe_irq_off() will report only the first ISA IRQ handled,
         potentially leading to a false negative.
      
      There was another bug that meant it ignored all error codes from
      request_irq() except -EBUSY, so it would 'succeed' despite this
      (possibly causing conflicts with other ISA devices).  This was fixed
      by ab08999d 'WARNING: some
      request_irq() failures ignored in el2_open()', which exposed bug 1.
      
      This patch:
      1. Replaces the use of probe_irq_{on,off}() with a real interrupt handler
      2. Adds a delay before checking the interrupt-seen flag
      3. Disables interrupts on all failure paths
      4. Distinguishes error codes from the second request_irq() call,
         consistently with the first
      
      Compile-tested only.
      
      Signed-off-by: default avatarBen Hutchings <ben@decadent.org.uk>
      Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
      b0cf4dfb
  7. Dec 03, 2009
  8. Sep 04, 2009
  9. Sep 03, 2009
  10. May 26, 2009
  11. Mar 27, 2009
  12. Jan 11, 2009
  13. Nov 25, 2008
  14. Oct 27, 2008
  15. Jul 04, 2008
  16. Oct 10, 2007
  17. Feb 09, 2007
  18. Dec 04, 2006
  19. Sep 13, 2006
  20. Jun 11, 2006
    • Randy Dunlap's avatar
      [PATCH] 3c5zz ethernet: fix section warnings · 96e672c7
      Randy Dunlap authored
      
      Priority: not critical; makes init code discardable.
      
      Fix section mismatch warnings:
      WARNING: drivers/net/3c501.o - Section mismatch: reference to .init.text:el1_probe from .text between 'init_module' (at offset 0x812) and 'cleanup_module'
      WARNING: drivers/net/3c503.o - Section mismatch: reference to .init.text: from .text between 'init_module' (at offset 0x661) and 'cleanup_card'
      WARNING: drivers/net/3c505.o - Section mismatch: reference to .init.text: from .text between 'init_module' (at offset 0x228d) and 'cleanup_module'
      WARNING: drivers/net/3c507.o - Section mismatch: reference to .init.text:el16_probe from .text between 'init_module' (at offset 0xa99) and 'cleanup_module'
      WARNING: drivers/net/3c523.o - Section mismatch: reference to .init.text: from .text between 'init_module' (at offset 0x12e7) and 'cleanup_module'
      WARNING: drivers/net/3c527.o - Section mismatch: reference to .init.text:mc32_probe from .text between 'init_module' (at offset 0xd8d) and 'cleanup_module'
      
      Signed-off-by: default avatarRandy Dunlap <rdunlap@xenotime.net>
      Signed-off-by: default avatarJeff Garzik <jeff@garzik.org>
      96e672c7
  21. Jan 09, 2006
    • Denis Vlasenko's avatar
      [PATCH] fix a few "warning: 'cleanup_card' defined but not used" · 64916f1e
      Denis Vlasenko authored
      
      These warnings are emitted if non-modular network drivers are built.
      Fixes just move cleanup_card() definitions into #ifdef MODULE region.
      
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/wd.c:131: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/3c503.c:152: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/ne.c:216: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/hp.c:106: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/hp-plus.c:142: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/smc-ultra.c:172: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/e2100.c:144: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/es3210.c:159: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/lne390.c:149: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/lance.c:313: warning: 'cleanup_card' defined but not used
      /.1/usr/srcdevel/kernel/linux-2.6.15-rc7.src/drivers/net/ac3200.c:127: warning: 'cleanup_card' defined but not used
      
      Signed-off-by: default avatarAndrew Morton <akpm@osdl.org>
      Signed-off-by: default avatarJeff Garzik <jgarzik@pobox.com>
      64916f1e
  22. May 12, 2005
  23. Apr 16, 2005
    • Linus Torvalds's avatar
      Linux-2.6.12-rc2 · 1da177e4
      Linus Torvalds authored
      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!
Loading