* Daniel Walker <[email protected]> wrote: > > This driver is scheduled for removal, so I'd not touch it anymore to > > avoid the possibility to introduce a lastminute regression. The new > > drivers (b43 and b43legacy) have this fixed (in a different way by > > completely removing it). > > When is the removal scheduled? $ grep -i bcm Documentation/feature-removal-schedule.txt $ might make sense to update this file. Ingo -- 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/
- Follow-Ups:
- Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
- From: Michael Buesch <[email protected]>
- Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
- References:
- [PATCH 1/3] ps3: vuart: fix error path locking
- From: Daniel Walker <[email protected]>
- [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
- From: Daniel Walker <[email protected]>
- Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
- From: Michael Buesch <[email protected]>
- Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
- From: Daniel Walker <[email protected]>
- [PATCH 1/3] ps3: vuart: fix error path locking
- Prev by Date: [PATCH] dpt_i2o: don't set DMA_64BIT_MASK [was: Re: [stable] broken dpt_i2o in 2.6.23 (was: ext2 check page: bad entry in directory) (fwd)]
- Next by Date: Re: [kvm-devel] [RFC] Proposed new directory layout for kvm and virtualization
- Previous by thread: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
- Next by thread: Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
- Index(es):
 |