Re: [patch 07/30] bcm43xx: Drain TX status before starting IRQs

* Larry Finger ([email protected]) wrote:
> The regression turns out to be a locking problem involving bcm43xx, 
> wpa_supplicant, and NetworkManager. The exact cause is unknown; however, 
> this patch is clearly not the problem. Please reinstate it for inclusion in 
> -stable.

Thanks for the follow-up, Larry.  It's queued for next -stable.

thanks,
-chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [patch 00/30] -stable review
    • From: Chris Wright <[email protected]>
  • [patch 07/30] bcm43xx: Drain TX status before starting IRQs
    • From: Chris Wright <[email protected]>
  • Re: [patch 07/30] bcm43xx: Drain TX status before starting IRQs
    • From: Larry Finger <[email protected]>

• Prev by Date: Re: Linux 2.6.18.3
• Next by Date: reiserfs NET=n build error
• Previous by thread: Re: [patch 07/30] bcm43xx: Drain TX status before starting IRQs
• Next by thread: Re: [patch 07/30] bcm43xx: Drain TX status before starting IRQs
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]