From: Larry Finger <Larry.Finger@lwfinger.net>
To: bcm43xx-dev@lists.berlios.de
Cc: wireless <linux-wireless@vger.kernel.org>
Subject: Problems with 2.6.30-rc1
Date: Wed, 08 Apr 2009 16:18:19 -0500 [thread overview]
Message-ID: <49DD149B.2060300@lwfinger.net> (raw)
In-Reply-To: <20090408192634.GB3717@samweis.home.lxtec.de>
If you are having problems with wireless networking using 2.6.30-rc1 from
Linus's Linux-2.6 git tree, the fix is the following (Note: This is _NOT_ needed
for wireless-testing!!!):
---
Fix try_then_request_module to use waiting __request_module again.
Signed-off-by: Andreas Schwab <schwab@linux-m68k.org>
---
include/linux/kmod.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Index: linux-2.6.30-rc1/include/linux/kmod.h
===================================================================
--- linux-2.6.30-rc1.orig/include/linux/kmod.h 2009-04-08 12:47:54.000000000 +0200
+++ linux-2.6.30-rc1/include/linux/kmod.h 2009-04-08 17:39:35.000000000 +0200
@@ -34,7 +34,7 @@ extern int __request_module(bool wait, c
#define request_module(mod...) __request_module(true, mod)
#define request_module_nowait(mod...) __request_module(false, mod)
#define try_then_request_module(x, mod...) \
- ((x) ?: (__request_module(false, mod), (x)))
+ ((x) ?: (__request_module(true, mod), (x)))
#else
static inline int request_module(const char *name, ...) { return -ENOSYS; }
static inline int request_module_nowait(const char *name, ...) { return -ENOSYS; }
--
next parent reply other threads:[~2009-04-08 21:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20090408182021.GA4112@aragorn.home.lxtec.de>
[not found] ` <200904082050.00327.mb@bu3sch.de>
[not found] ` <49DCF537.8000702@lwfinger.net>
[not found] ` <20090408192634.GB3717@samweis.home.lxtec.de>
2009-04-08 21:18 ` Larry Finger [this message]
2009-04-09 3:59 ` Problems with 2.6.30-rc1 gavron
2009-04-09 10:37 ` Sedat Dilek
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=49DD149B.2060300@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=bcm43xx-dev@lists.berlios.de \
--cc=linux-wireless@vger.kernel.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).