From: Takashi Iwai <tiwai@suse.de>
To: linux-next@vger.kernel.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Stephen Rothwell <sfr@canb.auug.org.au>,
Johannes Berg <johannes@sipsolutions.net>,
Rusty Russell <rusty@rustcorp.com.au>,
LKML <linux-kernel@vger.kernel.org>,
netdev@vger.kernel.org, video4linux-list@redhat.com
Subject: CONFIG_KMOD breakage in next kernel
Date: Wed, 20 Aug 2008 18:16:13 +0200 [thread overview]
Message-ID: <s5h3akzwtki.wl%tiwai@suse.de> (raw)
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.
My particular problem would be fixed by the patch below, but I found
CONFIG_KMOD is still referred in many places.
% find * -name '*.[ch]' | xargs grep -l CONFIG_KMOD
drivers/media/video/w9968cf.c
drivers/media/video/v4l2-common.c
drivers/media/video/v4l1-compat.c
drivers/media/video/usbvision/usbvision-video.c
drivers/media/video/usbvision/usbvision-core.c
drivers/media/video/vino.c
drivers/media/video/cpia.c
drivers/video/fbmem.c
drivers/md/md.c
drivers/net/irda/sir_dongle.c
drivers/net/pppox.c
drivers/net/ppp_generic.c
drivers/mtd/mtdpart.c
fs/char_dev.c
fs/exec.c
kernel/kmod.c
net/dccp/ccid.c
net/sunrpc/auth.c
net/ipv4/devinet.c
net/ipv4/inet_diag.c
net/ipv4/tcp_cong.c
net/bluetooth/af_bluetooth.c
net/sched/cls_api.c
net/sched/act_api.c
net/sched/ematch.c
net/sched/sch_api.c
net/can/af_can.c
net/core/rtnetlink.c
net/core/dev.c
net/decnet/dn_dev.c
net/netlink/af_netlink.c
net/socket.c
net/netfilter/nfnetlink.c
net/bridge/netfilter/ebtables.c
Anyone working on this? It must be trivial.
Or, revert the following for the time being until all these are fixed:
commit ba90ad7a589abdf59553a622c35cc149a348034f
Author: Johannes Berg <johannes@sipsolutions.net>
Date: Tue Jul 8 19:00:26 2008 +0200
remove CONFIG_KMOD
Now that nothing depends on it any more, remove CONFIG_KMOD.
Signed-off-by: Johannes Berg <johannes@sipsolutions.net>
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
thanks,
Takashi
---
diff --git a/fs/nls/nls_base.c b/fs/nls/nls_base.c
index 64965e1..9f1a54c 100644
--- a/fs/nls/nls_base.c
+++ b/fs/nls/nls_base.c
@@ -13,9 +13,6 @@
#include <linux/nls.h>
#include <linux/kernel.h>
#include <linux/errno.h>
-#ifdef CONFIG_KMOD
-#include <linux/kmod.h>
-#endif
#include <linux/spinlock.h>
static struct nls_table default_table;
@@ -216,7 +213,7 @@ static struct nls_table *find_nls(char *charset)
struct nls_table *load_nls(char *charset)
{
struct nls_table *nls;
-#ifdef CONFIG_KMOD
+#ifdef CONFIG_MODULES
int ret;
#endif
@@ -224,7 +221,7 @@ struct nls_table *load_nls(char *charset)
if (nls)
return nls;
-#ifdef CONFIG_KMOD
+#ifdef CONFIG_MODULES
ret = request_module("nls_%s", charset);
if (ret != 0) {
printk("Unable to load NLS charset %s\n", charset);
next reply other threads:[~2008-08-20 16:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 16:16 Takashi Iwai [this message]
2008-08-20 17:16 ` CONFIG_KMOD breakage in next kernel Marcel Holtmann
2008-08-20 18:44 ` Johannes Berg
2008-08-21 1:49 ` Marcel Holtmann
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=s5h3akzwtki.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--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=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).