Messages in this thread | | | Subject | Re: CONFIG_KMOD breakage in next kernel | From | Johannes Berg <> | Date | Wed, 20 Aug 2008 20:44:49 +0200 |
| |
On Wed, 2008-08-20 at 19:16 +0200, Marcel Holtmann wrote: > Hi guys, > > > 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.
johannes [unhandled content-type:application/pgp-signature] | |