From: Michael Buesch <mb@bu3sch.de>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Bcm43xx-dev@lists.berlios.de, linux-wireless@vger.kernel.org
Subject: Re: [PATCH] b43: Fix rfkill radio LED
Date: Thu, 13 Dec 2007 12:11:47 +0100 [thread overview]
Message-ID: <200712131211.47867.mb@bu3sch.de> (raw)
In-Reply-To: <4760c3db.qCB1sy2b6EqODHqS%Larry.Finger@lwfinger.net>
On Thursday 13 December 2007 06:32:11 Larry Finger wrote:
> Michael,
>
> I finally found the problem. It turned out that b43_rfkill_soft_toggle()
> was returning -EBUSY even when there was no error. I also changed the
Oh, damn. :)
> logic in the request_module("rfkill-input") section. Now, the code is
Ehm, no. Wait.
There was a
#ifdef CONFIG_RFKILL_INPUT_MODULE
That is only defined if rfkill-input is a module, right?
> only compiled if rfkill-input is not built-in.
--
Greetings Michael.
next prev parent reply other threads:[~2007-12-13 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-13 5:32 [PATCH] b43: Fix rfkill radio LED Larry Finger
2007-12-13 11:11 ` Michael Buesch [this message]
2007-12-13 17:24 ` Larry Finger
2007-12-13 17:58 ` Michael Buesch
-- strict thread matches above, loose matches on Subject: below --
2007-12-13 5:27 Larry Finger
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=200712131211.47867.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Bcm43xx-dev@lists.berlios.de \
--cc=Larry.Finger@lwfinger.net \
--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).