Hi Johannes, > > > I found that CONFIG_KMOD was already removed in linux-next tree. > > > This seems to result in many breakages. For example, I cannot mount a > > > FAT device automatically because of failure of automatic loading of > > > nls modules. > > > > > > My particular problem would be fixed by the patch below, but I found > > > CONFIG_KMOD is still referred in many places. > > > > I am happy to fix the net/bluetooth/ part, you someone has to put out a > > guideline how this should be fixed. > > Bluetooth was already part of http://lkml.org/lkml/2008/7/9/144 > > Basically, I got rid of CONFIG_KMOD, always enabling it when > CONFIG_MODULES is defined and making it a dummy no-op inline when not. I missed the patches, but that happens from time to time. Just looked at them and they look pretty nice. I like it this way. Acked-by: Marcel Holtmann <marcel@xxxxxxxxxxxx> Regards Marcel -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
