On Mon, 4 Oct 2010, Thorsten Glaser wrote: > Besides, it’s easier to get a bunch of modules that don’t do anything > except say the hardware they steer isn’t available to compile than to > change the config
Which modules are we talking about? In 2.6.32-23, debian patches speakup into drivers/staging but I don't see it in mainline drivers/accessibility or drivers/staging. If the bug is not in the mainline, then the fix should arguably be downstream too. (Policy seems to be that the mainline doesn't carry code that doesn't have in-tree users.) > (especially as the latter potentially has to be done for every new > kernel version, and I’d rather keep things working, as they seem to > change very quickly and nobody can keep up really). Is it easier to maintain local patches from one debian release to another than it is to maintain .config changes? Finn > > bye, > //mirabilos >
