From: Greg KH <greg@kroah.com>
To: kernel-janitors@vger.kernel.org
Subject: Re: [PATCH] staging/wlan-ng: reflects NL80211 API change
Date: Thu, 08 Jul 2010 20:14:47 +0000 [thread overview]
Message-ID: <20100708201447.GA2412@kroah.com> (raw)
In-Reply-To: <1277684197.9983.7.camel@lenovo>
On Sun, Jun 27, 2010 at 08:16:37PM -0400, Javier Martinez Canillas wrote:
> In today linux-next I got a compile error in wlan-ng:
>
> CC [M] drivers/staging/wlan-ng/p80211netdev.o
> In file included from drivers/staging/wlan-ng/p80211netdev.c:91:
> drivers/staging/wlan-ng/cfg80211.c:602: warning: ‘enum tx_power_setting’ declared inside parameter list
> drivers/staging/wlan-ng/cfg80211.c:602: warning: its scope is only this definition or declaration, which is probably not what you want
> drivers/staging/wlan-ng/cfg80211.c:602: error: parameter 2 (‘type’) has incomplete type
> drivers/staging/wlan-ng/cfg80211.c: In function ‘prism2_set_tx_power’:
> drivers/staging/wlan-ng/cfg80211.c:609: error: ‘TX_POWER_AUTOMATIC’ undeclared (first use in this function)
> drivers/staging/wlan-ng/cfg80211.c:609: error: (Each undeclared identifier is reported only once
> drivers/staging/wlan-ng/cfg80211.c:609: error: for each function it appears in.)
> make[1]: *** [drivers/staging/wlan-ng/p80211netdev.o] Error 1
> make: *** [_module_drivers/staging/wlan-ng] Error 2
>
> The problem is that the 802.11 netlink interface changed and the driver was not updated
This needs to go through the wireless tree, care to send it there? It
just caused a build error in my tree if I was to take it :(
thanks,
greg k-h
next prev parent reply other threads:[~2010-07-08 20:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 0:16 [PATCH] staging/wlan-ng: reflects NL80211 API change Javier Martinez Canillas
2010-07-08 20:14 ` Greg KH [this message]
2010-07-09 4:50 ` Javier Martinez Canillas
2010-07-09 15:05 ` Greg KH
2010-07-09 15:57 ` Javier Martinez Canillas
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=20100708201447.GA2412@kroah.com \
--to=greg@kroah.com \
--cc=kernel-janitors@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