From: Marcel Holtmann <marcel@holtmann.org>
To: Manuel Estrada Sainz <ranty@debian.org>
Cc: "Barry K. Nathan" <barryn@pobox.com>, Alan Cox <alan@redhat.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.4.22-pre10-ac1
Date: 02 Aug 2003 11:23:53 +0200 [thread overview]
Message-ID: <1059816240.22299.31.camel@pegasus> (raw)
In-Reply-To: <20030802063749.GA23189@ranty.pantax.net>
[-- Attachment #1: Type: text/plain, Size: 1270 bytes --]
Hi Manuel,
> > ccache gcc -D__KERNEL__ -I/home/barryn/lsx/kernels/2.4/build/linux-2.4.22-pre10-ac1/include -Wall -Wstrict-prototypes -Wno-trigraphs -Os -fno-strict-aliasing -fno-common -fomit-frame-pointer -pipe -mpreferred-stack-boundary=2 -march=athlon -DMODULE -DMODVERSIONS -include /home/barryn/lsx/kernels/2.4/build/linux-2.4.22-pre10-ac1/include/linux/modversions.h -nostdinc -iwithprefix include -DKBUILD_BASENAME=firmware_class -DEXPORT_SYMTAB -c firmware_class.c
> > firmware_class.c: In function `call_helper':
> > firmware_class.c:78: error: `hotplug_path' undeclared (first use in this function)
> > firmware_class.c:78: error: (Each undeclared identifier is reported only once
> > firmware_class.c:78: error: for each function it appears in.)
> > make[1]: *** [firmware_class.o] Error 1
> > make[1]: Leaving directory `/home/barryn/lsx/kernels/2.4/build/linux-2.4.22-pre10-ac1/lib'
> > make: *** [_mod_lib] Error 2
> [snip]
> > # CONFIG_HOTPLUG is not set
>
> CONFIG_HOTPLUG needs to be enabled, attached patch to make it explicit:
your patch didn't fix the problem, because it will be the same if some
internal driver needs request_firmware() and CONFIG_HOTPLUG is not set.
The call_helper() funtcion needs to be put into #idef's.
Regards
Marcel
[-- Attachment #2: patch-2.4.22-pre10-ac1-reqfrm-hotplug --]
[-- Type: text/x-patch, Size: 973 bytes --]
diff -urN linux-2.4.22-pre10-ac1/lib/firmware_class.c linux-2.4.22-pre10-ac1-reqfrm-hotplug/lib/firmware_class.c
--- linux-2.4.22-pre10-ac1/lib/firmware_class.c Sat Aug 2 10:50:04 2003
+++ linux-2.4.22-pre10-ac1-reqfrm-hotplug/lib/firmware_class.c Sat Aug 2 11:21:02 2003
@@ -67,6 +67,8 @@
static struct proc_dir_entry *proc_dir_timeout;
static struct proc_dir_entry *proc_dir;
+#ifdef CONFIG_HOTPLUG
+
static int
call_helper(char *verb, const char *name, const char *device)
{
@@ -126,7 +128,9 @@
envp[i++] = 0;
+#ifdef DEBUG
dbg("firmware: %s %s %s", argv[0], argv[1], verb);
+#endif
retval = call_usermodehelper(argv[0], argv, envp);
if (retval) {
@@ -137,6 +141,15 @@
kfree(envp);
return retval;
}
+#else
+
+static inline int
+call_helper(char *verb, const char *name, const char *device)
+{
+ return -ENOENT;
+}
+
+#endif /* CONFIG_HOTPLUG */
struct firmware_priv {
struct completion completion;
next prev parent reply other threads:[~2003-08-02 9:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-01 22:16 Linux 2.4.22-pre10-ac1 Alan Cox
2003-08-02 4:09 ` Barry K. Nathan
2003-08-02 6:37 ` Manuel Estrada Sainz
2003-08-02 9:23 ` Marcel Holtmann [this message]
2003-08-02 9:41 ` Manuel Estrada Sainz
2003-08-02 9:57 ` Marcel Holtmann
2003-08-02 12:29 ` Alan Cox
2003-08-02 13:42 ` Marcel Holtmann
2003-08-10 22:34 ` Manuel Estrada Sainz
2003-08-03 10:57 ` [patch] 2.4.22-pre10-ac1: fix tp600.c compile warning Adrian Bunk
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=1059816240.22299.31.camel@pegasus \
--to=marcel@holtmann.org \
--cc=alan@redhat.com \
--cc=barryn@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ranty@debian.org \
/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).