linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Gertjan van Wingerde <gwingerde@gmail.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: John Linville <linville@tuxdriver.com>,
	linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] mac80211: remove struct ieee80211_if_init_conf
Date: Mon, 07 Dec 2009 22:35:33 +0100	[thread overview]
Message-ID: <4B1D7525.6070506@gmail.com> (raw)
In-Reply-To: <1260177774.13866.27.camel@johannes.local>

On 12/07/09 10:22, Johannes Berg wrote:
> All its members (vif, mac_addr, type) are now available
> in the vif struct directly, so we can pass that instead
> of the conf struct. I generated this patch (except the
> mac80211 and header file changes) with this semantic
> patch:
> 
> @@
> identifier conf, fn, hw;
> type tp;
> @@
> tp fn(struct ieee80211_hw *hw,
> -struct ieee80211_if_init_conf *conf)
> +struct ieee80211_vif *vif)
> {
> <...
> (
> -conf->type
> +vif->type
> |
> -conf->mac_addr
> +vif->addr
> |
> -conf->vif
> +vif
> )
> ...>
> }
> 
> Signed-off-by: Johannes Berg <johannes@sipsolutions.net>

For the rt2x00 part:

Acked-by: Gertjan van Wingerde <gwingerde@gmail.com>

> ---
>  drivers/net/wireless/adm8211.c             |   12 +++---
>  drivers/net/wireless/at76c50x-usb.c        |    6 +--
>  drivers/net/wireless/ath/ar9170/main.c     |    8 ++--
>  drivers/net/wireless/ath/ath5k/base.c      |   18 ++++-----
>  drivers/net/wireless/ath/ath9k/main.c      |   28 +++++++-------
>  drivers/net/wireless/b43/main.c            |   26 ++++++-------
>  drivers/net/wireless/b43legacy/main.c      |   24 ++++++------
>  drivers/net/wireless/iwlwifi/iwl-core.c    |   20 +++++-----
>  drivers/net/wireless/iwlwifi/iwl-core.h    |    4 +-
>  drivers/net/wireless/libertas_tf/main.c    |   10 ++---
>  drivers/net/wireless/mac80211_hwsim.c      |   18 ++++-----
>  drivers/net/wireless/mwl8k.c               |   14 +++----
>  drivers/net/wireless/p54/main.c            |   12 +++---
>  drivers/net/wireless/rt2x00/rt2x00.h       |    4 +-
>  drivers/net/wireless/rt2x00/rt2x00mac.c    |   26 ++++++-------
>  drivers/net/wireless/rtl818x/rtl8180_dev.c |   14 +++----
>  drivers/net/wireless/rtl818x/rtl8187_dev.c |   12 +++---
>  drivers/net/wireless/wl12xx/wl1251_main.c  |   14 +++----
>  drivers/net/wireless/wl12xx/wl1271_main.c  |   10 ++---
>  drivers/net/wireless/zd1211rw/zd_mac.c     |   10 ++---
>  include/net/mac80211.h                     |   57 +++++++----------------------
>  net/mac80211/driver-ops.h                  |   12 +++---
>  net/mac80211/iface.c                       |   14 +------
>  net/mac80211/pm.c                          |    6 ---
>  net/mac80211/util.c                        |    9 +---
>  25 files changed, 172 insertions(+), 216 deletions(-)
> 

      reply	other threads:[~2009-12-07 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07  9:22 [PATCH] mac80211: remove struct ieee80211_if_init_conf Johannes Berg
2009-12-07 21:35 ` Gertjan van Wingerde [this message]

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=4B1D7525.6070506@gmail.com \
    --to=gwingerde@gmail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).