From: Johannes Berg <johannes@sipsolutions.net>
To: ath9k-devel@lists.ath9k.org
Subject: [ath9k-devel] [PATCH] ath9k: Fix a WARNING in suspend/resume with IBSS
Date: Sat, 02 Jun 2012 19:45:35 +0200 [thread overview]
Message-ID: <1338659135.12823.3.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4FCA30DE.4080805@qca.qualcomm.com>
Hi Mohammed,
> >>> You could just remove the entire check since the interface combinations
> >>> you advertise don't allow it, I think? Or just fix those
> >>> combinations :-)
> >>
> >> i did not check this before, thanks a lot for your inputs. will send a
> >> proper v2 after checking this out.
> >
> > If this is needed for stable, you might want to keep this patch& send
> > another one to remove it.
>
> thanks Johannes.
> i was looking at how to fix this properly in iface combination
> advertised to mac80211. got few doubts regarding this
>
> *if an interface type is not all advertised in the
> ieee80211_iface_combination then it cannot it be co-existing with any
> other interfaces ?
> please let me know is there some other way do that.
>
> if we advertise something like this
>
> static const struct ieee80211_iface_limit if_limits[] = {
> {set1
> .... },
> {set 2
> .... },
> };
>
> then interface types in set1 and set2 co-exist as per the logic in
> cfg80211_can_change_interface. is there already a way we can make
> set1 and set2 interface types mutually exclusive ? thanks!
The sets are mutually exclusive, and there are implied sets of each
interface with a max number of 1. So for example, in iwlwifi we don't
advertise IBSS in the combinations at all, because it's not compatible
with anything. In your case, I think the same applies, since you said
if the first interface is ADHOC we cannot have any other
interface. we cannot add an ADHOC interface if there is already
an interface is present
Thus, if you leave IBSS out of the combinations you should get the
desired behaviour of not being able to combine IBSS with any other
types.
johannes
next prev parent reply other threads:[~2012-06-02 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-01 6:39 [ath9k-devel] [PATCH] ath9k: Fix a WARNING in suspend/resume with IBSS Mohammed Shafi Shajakhan
2012-06-01 6:44 ` Johannes Berg
2012-06-01 7:09 ` Mohammed Shafi Shajakhan
2012-06-01 7:13 ` Johannes Berg
2012-06-02 15:27 ` Mohammed Shafi Shajakhan
2012-06-02 17:45 ` Johannes Berg [this message]
2012-06-02 18:14 ` Guido Iribarren
2012-06-02 18:30 ` Felix Fietkau
2012-06-04 15:46 ` Mohammed Shafi Shajakhan
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=1338659135.12823.3.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=ath9k-devel@lists.ath9k.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