From: Marcel Holtmann <marcel@holtmann.org>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Takashi Iwai <tiwai@suse.de>,
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: Thu, 21 Aug 2008 03:49:17 +0200 [thread overview]
Message-ID: <1219283357.7591.370.camel@violet.holtmann.net> (raw)
In-Reply-To: <1219257889.3502.13.camel@johannes.berg>
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@holtmann.org>
Regards
Marcel
next prev parent reply other threads:[~2008-08-21 1:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 16:16 CONFIG_KMOD breakage in next kernel Takashi Iwai
2008-08-20 17:16 ` Marcel Holtmann
2008-08-20 18:44 ` Johannes Berg
2008-08-21 1:49 ` Marcel Holtmann [this message]
2008-08-20 18:16 ` Johannes Berg
2008-08-25 0:13 ` Rusty Russell
2008-08-25 0:28 ` Stephen Rothwell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1219283357.7591.370.camel@violet.holtmann.net \
--to=marcel@holtmann.org \
--cc=akpm@linux-foundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=rusty@rustcorp.com.au \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
--cc=video4linux-list@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).