Hi, Lennart Sorensen wrote:Yeah, pick the right configuration. You can make it malfunction. I'm not too sure whether that will be always possible and I'm less sure we'll get enough test coverage over this kind of stuff. Yeah, theoretically, you're right. The problem is that what breaks when things go wrong. If you don't probe generic ports by default, harddisks won't be detected on some legacy systems but you can always prompt the user about loading the generic driver. If you probe generic ports by default, when things go wrong, you break modern machines in an unrecoverable (w/o reset) way. I'd rather choose bothering the user on legacy machines. thanks. -- tejun --
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Linus Torvalds | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| David Newall | Re: Slow DOWN, please!!! |
| Ian Campbell | Re: [PATCH] x86: Construct 32 bit boot time page tables in native format. |
| Matthias Scheler | Re: HEADS UP: timecounters (branch simonb-timecounters) merged into -current |
| Greg Troxel | Re: Interface to change NFS exports |
| Thor Lancelot Simon | metadata cache and memory fragmentation |
| YAMAMOTO Takashi | amap memory allocation |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | [GIT]: Networking |
| Dushan Tcholich | Re: ksoftirqd high cpu load on kernels 2.6.24 to 2.6.27-rc1-mm1 |
