All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lukasz Kucharczyk <lukasz.kucharczyk@tieto.com>
To: Johannes Berg <johannes@sipsolutions.net>,
	<chunkeey@googlemail.com>, <wey-yi.w.guy@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: fix interface combinations check.
Date: Thu, 12 Apr 2012 09:57:26 +0200	[thread overview]
Message-ID: <4F868AE6.7080003@tieto.com> (raw)
In-Reply-To: <1334204861.3788.20.camel@jlt3.sipsolutions.net>

On 04/12/2012 06:27 AM, Johannes Berg wrote:
> On Wed, 2012-04-11 at 14:55 +0200, Lukasz Kucharczyk wrote:
>> Signed-off-by: Lukasz Kucharczyk<lukasz.kucharczyk@tieto.com>
>
> Good catch, should this be Cc stable?

I think so, but I have only tested this with driver which is not yet 
upstreamed. It seems that only carl9170 and iwlwifi are using interface 
combinations. Christian, Wey, what do you think?

Lukasz

>
>> ---
>>   net/wireless/util.c |    2 +-
>>   1 files changed, 1 insertions(+), 1 deletions(-)
>>
>> diff --git a/net/wireless/util.c b/net/wireless/util.c
>> index 1b7a08d..957f256 100644
>> --- a/net/wireless/util.c
>> +++ b/net/wireless/util.c
>> @@ -989,7 +989,7 @@ int cfg80211_can_change_interface(struct cfg80211_registered_device *rdev,
>>   			if (rdev->wiphy.software_iftypes&  BIT(iftype))
>>   				continue;
>>   			for (j = 0; j<  c->n_limits; j++) {
>> -				if (!(limits[j].types&  iftype))
>> +				if (!(limits[j].types&  BIT(iftype)))
>>   					continue;
>>   				if (limits[j].max<  num[iftype])
>>   					goto cont;
>
>


      reply	other threads:[~2012-04-12  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-11 12:55 [PATCH] cfg80211: fix interface combinations check Lukasz Kucharczyk
2012-04-12  4:27 ` Johannes Berg
2012-04-12  7:57   ` Lukasz Kucharczyk [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=4F868AE6.7080003@tieto.com \
    --to=lukasz.kucharczyk@tieto.com \
    --cc=chunkeey@googlemail.com \
    --cc=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=wey-yi.w.guy@intel.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 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.