Kristen Carlson Accardi wrote:It's a one-off driver-specific interface that will have to be supported even after the same feature is available via libata core... that's not the path to scalable, sustainable engineering. I know user interfaces are annoying because you have to think about chips other than your own, but that's life. Other hardware vendors have to do it too. Letting each driver have a different user interface is /unfriendly/ to both developers users. It's easiest for Intel kernel developers, but that is not our target audience :) The biggest power savings for the largest amount of users can be had if you take a moment and figure out what's best for Linux, rather than what is best for Intel. Because you can be damned sure SATA users with non-AHCI chips want this power savings too... let's not put roadblocks to that in place in the beginning (by adding one-off interfaces). Jeff --
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| debian developer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [patch 00/40] 2.6.23-stable review, driver (sans network) changes |
| Roland Dreier | Re: Integration of SCST in the mainstream Linux kernel |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Arjan van de Ven | Re: [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Natalie Protasevich | [BUG] New Kernel Bugs |
