> i have no gripes about the current situation of wireless in linux-next,=20Clearly, you don't have a clue about wireless. I'll admit to being pissed off by statements like this because I personally spent a lot of time getting wireless code into shape for merging, and it took a long time. If we'd have merged the existing wireless drivers 2 years ago, we would have (at least) four 802.11 stacks in the kernel now, at least two legally questionable drivers (the ath5k legal situation would probably never have been cleared up, acx100 still isn't), no uniform API so it would be impossible to write userspace support tools etc. johannes
| Kok, Auke | Re: -mm merge plans for 2.6.23 - ioat/dma engine |
| Jeff Garzik | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Matthew Garrett | [PATCH] Remove process freezer from suspend to RAM pathway |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Jens Axboe | Re: [BUG] New Kernel Bugs |
git: | |
