[PATCH]wireless:ath9k Fix ath_print in xmit.c
in [Kernel]
|
Prev: [GIT PULL] Backlight updates for 2.6.35
Next: [PATCH 1/1] staging: hv: Fix race condition on IC channel initialization (modified)
From: Justin P. Mattock on 26 May 2010 12:50 ath_print in xmit.c should say "Reseting hardware" instead of Reaseting HAL!(since HAL is being fazed out). dmesg shows: [ 8660.899624] ath: Failed to stop TX DMA in 100 msec after killing last frame [ 8660.899676] ath: Unable to stop TxDMA. Reset HAL! Signed-off-by: Justin P. Mattock <justinmattock(a)gmail.com> --- drivers/net/wireless/ath/ath9k/xmit.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c index 3db1917..2a0558e 100644 --- a/drivers/net/wireless/ath/ath9k/xmit.c +++ b/drivers/net/wireless/ath/ath9k/xmit.c @@ -1198,7 +1198,7 @@ void ath_drain_all_txq(struct ath_softc *sc, bool retry_tx) int r; ath_print(common, ATH_DBG_FATAL, - "Unable to stop TxDMA. Reset HAL!\n"); + "Unable to stop TxDMA. Reseting hardware!\n"); spin_lock_bh(&sc->sc_resetlock); r = ath9k_hw_reset(ah, sc->sc_ah->curchan, false); -- 1.6.5.GIT -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Justin P. Mattock on 26 May 2010 13:10 On 05/26/2010 10:05 AM, Luis R. Rodriguez wrote: > On Wed, May 26, 2010 at 9:49 AM, Justin P. Mattock > <justinmattock(a)gmail.com> wrote: > >> ath_print in xmit.c should say "Reseting hardware" >> instead of Reaseting HAL!(since HAL is being fazed out). >> dmesg shows: >> [ 8660.899624] ath: Failed to stop TX DMA in 100 msec after killing last frame >> [ 8660.899676] ath: Unable to stop TxDMA. Reset HAL! >> >> >> Signed-off-by: Justin P. Mattock<justinmattock(a)gmail.com> >> >> --- >> drivers/net/wireless/ath/ath9k/xmit.c | 2 +- >> 1 files changed, 1 insertions(+), 1 deletions(-) >> >> diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c >> index 3db1917..2a0558e 100644 >> --- a/drivers/net/wireless/ath/ath9k/xmit.c >> +++ b/drivers/net/wireless/ath/ath9k/xmit.c >> @@ -1198,7 +1198,7 @@ void ath_drain_all_txq(struct ath_softc *sc, bool retry_tx) >> int r; >> >> ath_print(common, ATH_DBG_FATAL, >> - "Unable to stop TxDMA. Reset HAL!\n"); >> + "Unable to stop TxDMA. Reseting hardware!\n"); >> > Thanks for the patch but you need to send this to John, cc linux-wireless. > > Luis > > I'll resend with the proper Cc's Justin P. mattock -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Luis R. Rodriguez on 26 May 2010 13:10 On Wed, May 26, 2010 at 9:49 AM, Justin P. Mattock <justinmattock(a)gmail.com> wrote: > ath_print in xmit.c should say "Reseting hardware" > instead of Reaseting HAL!(since HAL is being fazed out). > dmesg shows: > [ 8660.899624] ath: Failed to stop TX DMA in 100 msec after killing last frame > [ 8660.899676] ath: Unable to stop TxDMA. Reset HAL! > > > Signed-off-by: Justin P. Mattock <justinmattock(a)gmail.com> > > --- > drivers/net/wireless/ath/ath9k/xmit.c | 2 +- > 1 files changed, 1 insertions(+), 1 deletions(-) > > diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c > index 3db1917..2a0558e 100644 > --- a/drivers/net/wireless/ath/ath9k/xmit.c > +++ b/drivers/net/wireless/ath/ath9k/xmit.c > @@ -1198,7 +1198,7 @@ void ath_drain_all_txq(struct ath_softc *sc, bool retry_tx) > int r; > > ath_print(common, ATH_DBG_FATAL, > - "Unable to stop TxDMA. Reset HAL!\n"); > + "Unable to stop TxDMA. Reseting hardware!\n"); Thanks for the patch but you need to send this to John, cc linux-wireless. Luis -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Justin P. Mattock on 26 May 2010 13:20 On 05/26/2010 10:05 AM, Luis R. Rodriguez wrote: > On Wed, May 26, 2010 at 9:49 AM, Justin P. Mattock > <justinmattock(a)gmail.com> wrote: > >> ath_print in xmit.c should say "Reseting hardware" >> instead of Reaseting HAL!(since HAL is being fazed out). >> dmesg shows: >> [ 8660.899624] ath: Failed to stop TX DMA in 100 msec after killing last frame >> [ 8660.899676] ath: Unable to stop TxDMA. Reset HAL! >> >> >> Signed-off-by: Justin P. Mattock<justinmattock(a)gmail.com> >> >> --- >> drivers/net/wireless/ath/ath9k/xmit.c | 2 +- >> 1 files changed, 1 insertions(+), 1 deletions(-) >> >> diff --git a/drivers/net/wireless/ath/ath9k/xmit.c b/drivers/net/wireless/ath/ath9k/xmit.c >> index 3db1917..2a0558e 100644 >> --- a/drivers/net/wireless/ath/ath9k/xmit.c >> +++ b/drivers/net/wireless/ath/ath9k/xmit.c >> @@ -1198,7 +1198,7 @@ void ath_drain_all_txq(struct ath_softc *sc, bool retry_tx) >> int r; >> >> ath_print(common, ATH_DBG_FATAL, >> - "Unable to stop TxDMA. Reset HAL!\n"); >> + "Unable to stop TxDMA. Reseting hardware!\n"); >> > Thanks for the patch but you need to send this to John, cc linux-wireless. > > Luis > > alright resent with the other patch I had kicking around.. (hopefully the right Cc's) cheers, Justin P. Mattock -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
From: Peter Stuge on 26 May 2010 19:20
Justin P. Mattock wrote: > ath_print in xmit.c should say "Reseting hardware" I think that should be "Resetting hardware" with two t:s. //Peter -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo(a)vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ |