From: Frank Sorenson <frank@tuxrocks.com>
To: art@usfltd.com
Cc: linux-kernel@vger.kernel.org, torvalds@osdl.org
Subject: [PATCH] Re: 2.6.19 git compile error - "current_is_keventd" [drivers/net/phy/libphy.ko] undefined
Date: Mon, 04 Dec 2006 23:08:47 -0600 [thread overview]
Message-ID: <4574FEDF.2010205@tuxrocks.com> (raw)
In-Reply-To: <20061204180731.jeedbekf4f0g8ww0@69.222.0.225>
art@usfltd.com wrote:
> to: linux-kernel@vger.kernel.org
> cc: torvalds@osdl.org
>
> 2006/12/04/18:00 CST
>
> Building modules, stage 2.
> Kernel: arch/x86_64/boot/bzImage is ready (#2)
> MODPOST 1256 modules
> WARNING: "current_is_keventd" [drivers/net/phy/libphy.ko] undefined!
> make[1]: *** [__modpost] Error 1
> make: *** [modules] Error 2
>
> xboom
Here's a patch with the easy fix, but I'm not certain it's a permanent fix.
Frank
This patch fixes a compile error when CONFIG_PHYLIB is a module.
Signed-off-by: Frank Sorenson <frank@tuxrocks.com>
---
kernel/workqueue.c | 1 +
1 file changed, 1 insertion(+)
Index: linux-2.6.19-fs1/kernel/workqueue.c
===================================================================
--- linux-2.6.19-fs1.orig/kernel/workqueue.c 2006-12-04
22:21:06.000000000 -0600
+++ linux-2.6.19-fs1/kernel/workqueue.c 2006-12-04 22:59:55.000000000 -0600
@@ -608,6 +608,7 @@
return ret;
}
+EXPORT_SYMBOL_GPL(current_is_keventd);
#ifdef CONFIG_HOTPLUG_CPU
/* Take the work from this (downed) CPU. */
prev parent reply other threads:[~2006-12-05 5:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-05 0:07 2.6.19 git compile error - "current_is_keventd" [drivers/net/phy/libphy.ko] undefined art
2006-12-05 1:29 ` Horst H. von Brand
2006-12-05 3:37 ` Linus Torvalds
2006-12-05 18:31 ` Maciej W. Rozycki
2006-12-05 20:09 ` Jan Engelhardt
2006-12-05 5:08 ` Frank Sorenson [this message]
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=4574FEDF.2010205@tuxrocks.com \
--to=frank@tuxrocks.com \
--cc=art@usfltd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.