Re: CONFIG_KMOD breakage in next kernel

From: Johannes Berg <johannes@sipsolutions.net>
To: Takashi Iwai <tiwai@suse.de>
Cc: linux-next@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Rusty Russell <rusty@rustcorp.com.au>,
	LKML <linux-kernel@vger.kernel.org>,
	netdev@vger.kernel.org, video4linux-list@redhat.com
Subject: Re: CONFIG_KMOD breakage in next kernel
Date: Wed, 20 Aug 2008 20:16:05 +0200	[thread overview]
Message-ID: <1219256165.3502.10.camel@johannes.berg> (raw)
In-Reply-To: <s5h3akzwtki.wl%tiwai@suse.de>

[-- Attachment #1: Type: text/plain, Size: 747 bytes --]

Hi,

> 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.

This is odd. I had posted a long series of patches removing all of the
users I had found (similar grep like the one you used), see
http://lkml.org/lkml/2008/7/9/150 for the whole thread.

For some reason, only seven of those eleven patches ended up in the
kernel, you had taken the alsa one and Rusty posted only six of them.

I'd hope that the patches posted at the URL above still apply, and I
sure intended the series to go in as posted with the removal of
CONFIG_KMOD coming last.

johannes

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]