From: Larry Finger <larry.finger@lwfinger.net>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Michael Buesch <mb@bu3sch.de>, wireless <linux-wireless@vger.kernel.org>
Subject: Re: Error in compilation of b43
Date: Fri, 28 Sep 2007 08:36:02 -0500 [thread overview]
Message-ID: <46FD0342.3020401@lwfinger.net> (raw)
In-Reply-To: <1190979092.5021.37.camel@johannes.berg>
Johannes Berg wrote:
> On Thu, 2007-09-27 at 23:38 -0500, Larry Finger wrote:
>=20
>> drivers/net/wireless/b43/rfkill.c:112: error: implicit declaration o=
f function =E2=80=98rfkill_get_led_name=E2=80=99
>> drivers/net/wireless/b43/rfkill.c:112: warning: return makes pointer=
from integer without a cast
>>
>> I assume that I missed some critical patch. Can you tell me which on=
e it is?
>=20
> Looks like "[PATCH] rfkill: Add support for an rfkill LED" might be i=
t.
That patch fixed the implicit declaration of rfkill_get_led_name, but I=
still get the other error
In file included from drivers/net/wireless/b43/rfkill.c:25:
drivers/net/wireless/b43/rfkill.h:17: error: field =E2=80=98notify_work=
=E2=80=99 has incomplete type
drivers/net/wireless/b43/rfkill.c: In function =E2=80=98b43_notify_rfki=
ll_press=E2=80=99:
drivers/net/wireless/b43/rfkill.c:31: warning: type defaults to =E2=80=98=
int=E2=80=99 in declaration of =E2=80=98__mptr=E2=80=99
drivers/net/wireless/b43/rfkill.c:31: warning: initialization from inco=
mpatible pointer type
Larry
-
To unsubscribe from this list: send the line "unsubscribe linux-wireles=
s" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-09-28 13:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 4:38 Error in compilation of b43 Larry Finger
2007-09-28 11:31 ` Johannes Berg
2007-09-28 13:36 ` Larry Finger [this message]
2007-09-28 13:36 ` Michael Buesch
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=46FD0342.3020401@lwfinger.net \
--to=larry.finger@lwfinger.net \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=mb@bu3sch.de \
/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).