1. 19 Dec, 2011 8 commits
  2. 16 Dec, 2011 1 commit
  3. 15 Dec, 2011 1 commit
  4. 14 Dec, 2011 1 commit
  5. 13 Dec, 2011 6 commits
  6. 14 Sep, 2011 6 commits
  7. 22 Aug, 2011 1 commit
  8. 19 Jul, 2011 1 commit
  9. 08 Jul, 2011 2 commits
  10. 07 Jul, 2011 1 commit
  11. 22 Jun, 2011 1 commit
  12. 01 Jun, 2011 3 commits
  13. 26 May, 2011 1 commit
  14. 16 May, 2011 1 commit
  15. 11 May, 2011 1 commit
  16. 29 Apr, 2011 1 commit
    • John W. Linville's avatar
      b43: avoid uninitialized variable warnings in phy_n · 2eeb6fd0
      John W. Linville authored
      
      
        CC [M]  drivers/net/wireless/b43/phy_n.o
      drivers/net/wireless/b43/phy_n.c: In function ‘b43_nphy_set_channel’:
      drivers/net/wireless/b43/phy_n.c:3848:47: warning: ‘tabent_r2’ may be used uninitialized in this function
      drivers/net/wireless/b43/phy_n.c:3849:47: warning: ‘tabent_r3’ may be used uninitialized in this function
      drivers/net/wireless/b43/phy_n.c: In function ‘b43_nphy_poll_rssi.clone.14’:
      drivers/net/wireless/b43/phy_n.c:2270:6: warning: ‘save_regs_phy$7’ may be used uninitialized in this function
      drivers/net/wireless/b43/phy_n.c:2270:6: warning: ‘save_regs_phy$8’ may be used uninitialized in this function
      
      FWIW, the usage of these variables is goverened by checks that match
      their initializations.  So, I think these are actually false warnings.
      Still, I would rather avoid the warning SPAM...
      Signed-off-by: default avatarJohn W. Linville <linville@tuxdriver.com>
      2eeb6fd0
  17. 04 Mar, 2011 2 commits
  18. 23 Feb, 2011 2 commits