On Fri, 2007-12-14 at 01:43 +0100, Michael Buesch wrote: > Oh come on. b43 is more than a year old now. How long should we wait? > Two or three? Forever? > Any pointers to the advantages of b43? Harvey -- 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]>
- 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: "Ray Lee" <[email protected]>
- Re: [PATCH 3/3] net: wireless: bcm43xx: big_buffer_sem semaphore to mutex
- From: Michael Buesch <[email protected]>
- [PATCH 1/3] ps3: vuart: fix error path locking
- Prev by Date: Re: [RFC PATCH 08/12] PAT 64b: coherent mmap and sysfs bin ioctl
- Next by Date: Re: [PATCH] fix page_alloc for larger I/O segments (improved)
- 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):
 |