From: Johannes Berg <johannes@sipsolutions.net>
To: dkiran@marvell.com
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH 1/3] Libertas: cfg80211 support
Date: Wed, 23 Jun 2010 10:25:56 +0200 [thread overview]
Message-ID: <1277281556.3642.6.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1276533086.18884.9.camel@pe-lt028>
On Mon, 2010-06-14 at 22:01 +0530, Kiran Divekar wrote:
> Holger Schurig's patch (https://patchwork.kernel.org/patch/64286/)
> is rebased to latest wireless-testing tree.
+drivers/net/wireless/libertas/cfg.c:1844:13: warning: incorrect type in assignment (different base types)
+drivers/net/wireless/libertas/cfg.c:1844:13: expected unsigned short [unsigned] [usertype] capability
+drivers/net/wireless/libertas/cfg.c:1844:13: got restricted __le16 [usertype] <noident>
+drivers/net/wireless/libertas/cmdresp.c:106:5: warning: symbol 'lbs_ret_802_11d_domain_info' was not declared. Should it be static?
I'm guessing this patchset is at fault.
johannes
next prev parent reply other threads:[~2010-06-23 8:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-14 16:31 [PATCH 1/3] Libertas: cfg80211 support Kiran Divekar
2010-06-14 12:40 ` Johannes Berg
2010-06-15 13:48 ` Holger Schurig
2010-06-23 8:25 ` Johannes Berg [this message]
2010-06-23 14:37 ` [PATCH 1/3] libertas: fix build error due to undefined symbol John W. Linville
2010-06-23 23:24 ` Dan Williams
2010-06-23 14:37 ` [PATCH 2/3] libertas: unmangle capability value John W. Linville
2010-06-23 23:24 ` Dan Williams
2010-06-23 14:37 ` [PATCH 3/3] libertas: mark lbs_ret_802_11d_domain_info static John W. Linville
2010-06-23 23:24 ` Dan Williams
2010-06-24 5:38 ` [PATCH 1/3] Libertas: cfg80211 support Kiran Divekar
2010-06-24 6:03 ` Johannes Berg
-- strict thread matches above, loose matches on Subject: below --
2010-06-05 6:20 Kiran Divekar
2010-06-08 13:30 ` John W. Linville
2010-05-18 12:33 Kiran Divekar
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=1277281556.3642.6.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=dkiran@marvell.com \
--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).