From: "Arend van Spriel" <arend@broadcom.com>
To: "Johannes Berg" <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org,
"Johannes Berg" <johannes.berg@intel.com>
Subject: Re: [RFC 13/17] nl80211: move scan API to wdev
Date: Tue, 19 Jun 2012 18:49:58 +0200 [thread overview]
Message-ID: <4FE0ADB6.5080105@broadcom.com> (raw)
In-Reply-To: <1340117456-10154-14-git-send-email-johannes@sipsolutions.net>
On 06/19/2012 04:50 PM, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
>
> The new P2P Device will have to be able to scan for
> P2P search, so move scanning to use struct wireless_dev
> instead of struct net_device.
>
> Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> ---
> diff --git a/drivers/net/wireless/ath/ath6kl/cfg80211.c b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> index 404e87c..a507b6e 100644
> --- a/drivers/net/wireless/ath/ath6kl/cfg80211.c
> +++ b/drivers/net/wireless/ath/ath6kl/cfg80211.c
> @@ -908,11 +908,11 @@ static int ath6kl_set_probed_ssids(struct ath6kl *ar,
> return 0;
> }
>
> -static int ath6kl_cfg80211_scan(struct wiphy *wiphy, struct net_device *ndev,
> +static int ath6kl_cfg80211_scan(struct wiphy *wiphy,
> struct cfg80211_scan_request *request)
Lot of indent issues in this variety of drivers. Do you care to fix that
as well or leave it to .... whom it may concern.
Gr. AvS
next prev parent reply other threads:[~2012-06-19 16:50 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-19 14:50 [RFC 0/17] add P2P Device support Johannes Berg
2012-06-19 14:50 ` [RFC 01/17] cfg80211: make some functions static Johannes Berg
2012-06-19 14:50 ` [RFC 02/17] nl80211: refactor __cfg80211_rdev_from_info Johannes Berg
2012-06-19 14:50 ` [RFC 03/17] nl80211: fix netns separation Johannes Berg
2012-06-19 14:50 ` [RFC 04/17] nl80211: change __cfg80211_rdev_from_info Johannes Berg
2012-06-19 14:50 ` [RFC 05/17] nl80211: use __cfg80211_rdev_from_attrs for testmode Johannes Berg
2012-06-19 14:50 ` [RFC 06/17] nl80211: prepare for non-netdev wireless devs Johannes Berg
2012-06-25 13:46 ` Eliad Peller
2012-06-25 14:12 ` Johannes Berg
2012-06-19 14:50 ` [RFC 07/17] nl80211: add NL80211_FLAG_NEED_WDEV Johannes Berg
2012-06-19 14:50 ` [RFC 08/17] nl80211: retrieve interface data by wdev Johannes Berg
2012-06-19 14:50 ` [RFC 09/17] nl80211: don't assume wdev->netdev exists Johannes Berg
2012-06-19 14:50 ` [RFC 10/17] cfg80211: use wdev in some APIs Johannes Berg
2012-06-19 14:50 ` [RFC 11/17] cfg80211: use wireless_dev for interface management Johannes Berg
2012-06-19 14:50 ` [RFC 12/17] nl80211: send interface after creation Johannes Berg
2012-06-19 14:50 ` [RFC 13/17] nl80211: move scan API to wdev Johannes Berg
2012-06-19 16:49 ` Arend van Spriel [this message]
2012-06-19 16:53 ` Johannes Berg
2012-06-19 14:50 ` [RFC 14/17] mac80211: remove unused function Johannes Berg
2012-06-19 14:50 ` [RFC 15/17] cfg80211: add P2P Device abstraction Johannes Berg
2012-06-25 15:20 ` Eliad Peller
2012-06-25 15:48 ` Johannes Berg
2012-06-25 16:05 ` Eliad Peller
2012-06-25 16:16 ` Johannes Berg
2012-06-25 17:07 ` Johannes Berg
2012-06-19 14:50 ` [RFC 16/17] mac80211: make ieee80211_check_concurrent_iface netdev-independent Johannes Berg
2012-06-19 14:50 ` [RFC 17/17] mac80211: support P2P Device abstraction Johannes Berg
2012-06-25 8:06 ` [RFC 0/17] add P2P Device support Johannes Berg
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=4FE0ADB6.5080105@broadcom.com \
--to=arend@broadcom.com \
--cc=johannes.berg@intel.com \
--cc=johannes@sipsolutions.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.