James Bottomley <[email protected]> writes: > One of the touted benefits of Linux is that we run on old hardware. > Unless the driver is demonstrably wrong (and they do become so as the > APIs evolve) Sure, I expect they do - but nobody is able to check. > The reverse (how do you know if someone's still using the driver) is > equally hard to determine. Sure. That's way I asked if we could make it easier. -- Krzysztof Halasa - 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: [2.6 patch] remove the broken SCSI_SEAGATE driver
- From: Arjan van de Ven <[email protected]>
- Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- References:
- [2.6 patch] remove the broken SCSI_SEAGATE driver
- From: Adrian Bunk <[email protected]>
- Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- From: James Bottomley <[email protected]>
- Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- From: Adrian Bunk <[email protected]>
- Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- From: Krzysztof Halasa <[email protected]>
- Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- From: James Bottomley <[email protected]>
- Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- From: Krzysztof Halasa <[email protected]>
- Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- From: James Bottomley <[email protected]>
- [2.6 patch] remove the broken SCSI_SEAGATE driver
- Prev by Date: Re: r8169 on n2100 (was Re: r8169 mac address change (was Re: [0/3] 2.6.19-rc2: known regressions))
- Next by Date: RE: GPL only modules
- Previous by thread: Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- Next by thread: Re: [2.6 patch] remove the broken SCSI_SEAGATE driver
- Index(es):
 |