Finn Thain dixit: >Which modules are we talking about? In 2.6.32-23, debian patches speakup >into drivers/staging
Yes. They are, however, compiled. This is a problem for me. At the moment, the one important thing for me is to get this &*#)*^&*( stuff to compile so we can go on with migration to TLS. I cannot upload modified source to unstable, so patches must go into the official Debian packages. Patches are only accepted if they are accepted by “someone” – so if they live in linux-m68k for a while it’s okay. http://kernel-handbook.alioth.debian.org/ch-source.html#s-acceptance Besides, this seems like a simple fix or an accidental omission to me. What is with all this bikeshedding? Some macros are not available on m68k if CONFIG_ISA is not set, but they are available “almost” or even really everywhere else, so drivers use them, so m68k is buggy in not providing them. (Outsider’s PoV.) bye, //mirabilos -- 16:47⎜«mika:#grml» .oO(mira ist einfach gut....) 23:22⎜«mikap:#grml» mirabilos: und dein bootloader ist geil :) 23:29⎜«mikap:#grml» und ich finds saugeil dass ich ein bsd zum booten mit grml hab, das muss ich dann gleich mal auf usb-stick installieren -- Michael Prokop über MirOS bsd4grml -- To unsubscribe from this list: send the line "unsubscribe linux-m68k" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
