All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Thomas Pedersen <c_tpeder@qca.qualcomm.com>
Cc: <ath6kl-devel@qualcomm.com>, <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] ath6kl: handle concurrent AP-STA channel switches
Date: Thu, 12 Apr 2012 09:56:29 +0300	[thread overview]
Message-ID: <4F867C9D.9070603@qca.qualcomm.com> (raw)
In-Reply-To: <1333744548-18028-2-git-send-email-c_tpeder@qca.qualcomm.com>

On 04/06/2012 11:35 PM, Thomas Pedersen wrote:
> If an ath6kl AP vif is beaconing on one channel, and a STA vif
> associates on a different channel, a WMI_DISCONNECT event will be sent
> to the AP vif. Make the AP vif follow the STA interface, and notify
> userspace.
> 
> Signed-off-by: Thomas Pedersen <c_tpeder@qca.qualcomm.com>

Thanks, applied. But there was a sparse warning:

drivers/net/wireless/ath/ath6kl/main.c:599:24: warning: incorrect type
in assignment (different base types)
drivers/net/wireless/ath/ath6kl/main.c:599:24:    expected unsigned
short [unsigned] [usertype] next_chan
drivers/net/wireless/ath/ath6kl/main.c:599:24:    got restricted __le16
[usertype] <noident>

I fixed it like this:

	vif->next_chan = channel;
	vif->profile.ch = cpu_to_le16(channel);

Please check my changes.

Kalle

  parent reply	other threads:[~2012-04-12  6:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-06 20:35 [PATCH v3 1/2] cfg80211: add channel switch notify event Thomas Pedersen
2012-04-06 20:35 ` [PATCH v3 2/2] ath6kl: handle concurrent AP-STA channel switches Thomas Pedersen
2012-04-09 15:05   ` Kalle Valo
2012-04-11 19:35     ` John W. Linville
2012-04-12  6:56   ` Kalle Valo [this message]
2012-04-12  3:37 ` [PATCH v3 1/2] cfg80211: add channel switch notify event 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=4F867C9D.9070603@qca.qualcomm.com \
    --to=kvalo@qca.qualcomm.com \
    --cc=ath6kl-devel@qualcomm.com \
    --cc=c_tpeder@qca.qualcomm.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 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.