1. 25 5月, 2014 1 次提交
  2. 23 5月, 2014 1 次提交
  3. 16 5月, 2014 1 次提交
  4. 14 5月, 2014 1 次提交
  5. 25 3月, 2014 1 次提交
  6. 24 3月, 2014 1 次提交
  7. 17 1月, 2014 1 次提交
  8. 16 1月, 2014 1 次提交
  9. 01 1月, 2014 1 次提交
  10. 15 11月, 2013 1 次提交
  11. 22 10月, 2013 2 次提交
  12. 03 10月, 2013 1 次提交
  13. 16 9月, 2013 1 次提交
  14. 31 8月, 2013 2 次提交
  15. 06 8月, 2013 1 次提交
    • J
      net: micrel: Staticize local functions · 51a700db
      Jingoo Han 提交于
      These local functions are used only in this file.
      Fix the following sparse warnings:
      
      drivers/net/ethernet/micrel/ks8842.c:708:6: warning: symbol 'ks8842_handle_rx' was not declared. Should it be static?
      drivers/net/ethernet/micrel/ks8842.c:718:6: warning: symbol 'ks8842_handle_tx' was not declared. Should it be static?
      drivers/net/ethernet/micrel/ks8842.c:727:6: warning: symbol 'ks8842_handle_rx_overrun' was not declared. Should it be static?
      drivers/net/ethernet/micrel/ks8842.c:735:6: warning: symbol 'ks8842_tasklet' was not declared. Should it be static?
      drivers/net/ethernet/micrel/ks8851_mll.c:691:6: warning: symbol 'ks_enable_qmu' was not declared. Should it be static?
      Signed-off-by: NJingoo Han <jg1.han@samsung.com>
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      51a700db
  16. 20 6月, 2013 1 次提交
  17. 28 5月, 2013 2 次提交
  18. 17 4月, 2013 1 次提交
  19. 09 4月, 2013 2 次提交
  20. 08 4月, 2013 1 次提交
  21. 30 3月, 2013 1 次提交
  22. 21 3月, 2013 1 次提交
  23. 12 3月, 2013 1 次提交
  24. 30 1月, 2013 1 次提交
  25. 04 1月, 2013 1 次提交
  26. 20 12月, 2012 1 次提交
    • L
      ksz884x: fix receive polling race condition · 4945106d
      Lennert Buytenhek 提交于
      The ksz884x driver does receive processing in a custom tasklet, and
      seems to be assuming that since it takes its private interface spinlock
      with spin_lock_irq(), it won't be running concurrently with its own
      interrupt handler, as it cannot be preempted by it, but since its
      interrupt handler doesn't do any locking whatsoever, the receive
      processing tasklet and interrupt handler can end up running concurrently
      on different CPUs.
      
      As a result of this, the ksz884x receive path ends up locking up fairly
      easily, when the receive processing tasklet's reenabling of receive
      interrupts (due to it being done with polling the receive ring) races
      with the interrupt handler's disabling of receive interrupts (due to a
      new receive interrupt coming in) resulting in the receive interrupt
      being masked but the receive processing tasklet not being scheduled.
      
      Fix this by making the ksz884x interrupt handler take its private
      interface spinlock.  This requires upgrading the spin_lock() in the
      transmit cleanup tasklet to a spin_lock_irq(), as otherwise the IRQ
      handler can preempt transmit cleanup and deadlock the system, but
      with those two changes, no more receive lockups have been observed.
      Reported-by: NChris Healy <cphealy@gmail.com>
      Signed-off-by: NLennert Buytenhek <buytenh@wantstofly.org>
      
      ----
      Signed-off-by: NDavid S. Miller <davem@davemloft.net>
      4945106d
  27. 08 12月, 2012 1 次提交
  28. 04 12月, 2012 1 次提交
  29. 20 11月, 2012 1 次提交
  30. 19 11月, 2012 1 次提交
  31. 15 11月, 2012 1 次提交
  32. 08 11月, 2012 1 次提交
  33. 04 11月, 2012 1 次提交
  34. 17 7月, 2012 1 次提交
  35. 11 7月, 2012 2 次提交