On Tue, Jun 10, 2008 at 06:52:22PM -0400, Theodore Tso wrote:I'm asking for the rule to be bent for this tree, not that the whole nature of linux-next is changing. -staging is for only whole new drivers/filesystems, not changes/features to existing code that is not yet ready for merging. The main reason these drivers are not in mainline is usually: - coding style issues - sparse cleanups needed - ioctl 32/64 cleanups - locking review - direct access to hardware through memory pointers (only works on x86) If you look at what I currently have, there's nothing earth-shattering there, but there is stuff that users can use to get hardware to work that currently is not supported on kernel.org kernels at all. It would be nice if distros also pick it up if they want to support these devices and give me some feedback. There are 2 big network drivers in there that support a wide range of devices that some people would like to see working :) thanks, greg k-h --
| Frans Pop | top displaying 9999% CPU usage |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Chuck Ebbert | Why do so many machines need "noapic"? |
| Andy Whitcroft | clam |
git: | |
| David Miller | [GIT]: Networking |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Christoph Lameter | Network latency regressions from 2.6.22 to 2.6.29 |
