From: "John W. Linville" <linville@tuxdriver.com>
To: Joe Perches <joe@perches.com>
Cc: linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org,
orinoco-users@lists.sourceforge.net,
orinoco-devel@lists.sourceforge.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] wireless: Make and use const struct ieee80211_channel
Date: Thu, 5 May 2011 14:49:34 -0400 [thread overview]
Message-ID: <20110505184934.GB3005@tuxdriver.com> (raw)
In-Reply-To: <cover.1304054543.git.joe@perches.com>
These patches generated a lot of warnings in net/mac80211. Did you
actually build them?
On Thu, Apr 28, 2011 at 10:25:06PM -0700, Joe Perches wrote:
> Joe Perches (2):
> wireless: Make struct ieee80211_channel const where possible
> wireless: Use const struct ieee80211_channel where possible
>
> drivers/net/wireless/iwlegacy/iwl-4965-lib.c | 2 +-
> drivers/net/wireless/iwlegacy/iwl3945-base.c | 2 +-
> drivers/net/wireless/iwlwifi/iwl-agn-lib.c | 2 +-
> drivers/net/wireless/iwmc3200wifi/cfg80211.c | 4 +-
> drivers/net/wireless/libertas/cfg.c | 2 +-
> drivers/net/wireless/mwifiex/cfg80211.c | 9 ++++---
> drivers/net/wireless/orinoco/cfg.c | 2 +-
> drivers/net/wireless/rndis_wlan.c | 9 ++++---
> drivers/net/wireless/wl1251/cmd.c | 2 +-
> drivers/net/wireless/wl1251/cmd.h | 2 +-
> include/net/cfg80211.h | 34 +++++++++++++-------------
> net/wireless/chan.c | 10 ++++----
> net/wireless/core.h | 14 ++++++----
> net/wireless/debugfs.c | 2 +-
> net/wireless/ibss.c | 6 ++--
> net/wireless/mlme.c | 15 ++++++-----
> net/wireless/nl80211.c | 31 ++++++++++++-----------
> net/wireless/nl80211.h | 9 ++++---
> net/wireless/reg.c | 11 ++++----
> net/wireless/reg.h | 4 +-
> net/wireless/scan.c | 6 ++--
> net/wireless/wext-sme.c | 2 +-
> 22 files changed, 94 insertions(+), 86 deletions(-)
>
> --
> 1.7.5.rc3.dirty
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-05-05 18:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 5:25 [PATCH 0/2] wireless: Make and use const struct ieee80211_channel Joe Perches
2011-04-29 5:25 ` [PATCH 1/2] wireless: Make struct ieee80211_channel const where possible Joe Perches
2011-04-29 7:11 ` Johannes Berg
2011-04-29 5:25 ` [PATCH 2/2] wireless: Use const struct ieee80211_channel " Joe Perches
2011-05-05 18:49 ` John W. Linville [this message]
2011-05-05 22:21 ` [PATCH 0/2] wireless: Make and use const struct ieee80211_channel Joe Perches
2011-05-06 13:19 ` John W. Linville
2011-05-06 16:10 ` Joe Perches
2011-05-11 16:57 ` John W. Linville
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=20110505184934.GB3005@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=joe@perches.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=orinoco-devel@lists.sourceforge.net \
--cc=orinoco-users@lists.sourceforge.net \
/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).