Message-ID: <1340875671.4491.25.camel@jlt3.sipsolutions.net> (sfid-20120628_112756_486731_31BF33A0)
Subject: Re: [RFC v3] initial channel context implementation
From: Johannes Berg <johannes@sipsolutions.net>
To: Michal Kazior <michal.kazior@tieto.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Date: Thu, 28 Jun 2012 11:27:51 +0200
In-Reply-To: <4FEC1BDF.8080607@tieto.com>
References: <1340714242-20032-1-git-send-email-michal.kazior@tieto.com>
	     <1340718188.14634.47.camel@jlt3.sipsolutions.net>
	     <4FEAB698.5070309@tieto.com>
	    <1340784614.8305.8.camel@jlt3.sipsolutions.net>
	    <4FEADCAE.5080508@tieto.com>
	   <1340795424.11012.11.camel@jlt3.sipsolutions.net>
	   <4FEAFFF1.7080706@tieto.com>
	  <1340805730.11012.33.camel@jlt3.sipsolutions.net>
	  <4FEC015B.4020603@tieto.com>
	 <1340871351.4491.19.camel@jlt3.sipsolutions.net>
	 <4FEC1BDF.8080607@tieto.com>
Content-Type: text/plain; charset="UTF-8"
Mime-Version: 1.0
Sender: linux-wireless-owner@vger.kernel.org

On Thu, 2012-06-28 at 10:54 +0200, Michal Kazior wrote:

> >>> Today mac80211 just updates it, yeah.
> >>
> >> Should I send the ,,respect channels in iface combinations'' as a
> >> [PATCH] now, or should the CSA issue (in cfg80211) be addressed first?
> >
> > Good question. Even if we don't do CSA first, I guess we don't really
> > break anything right now, do we? And if the driver/mac80211 just changes
> > the channel, that means it could seem to go over the limit of 1 channel
> > but things just break down like they do today?
> 
> Yeah, probably. We might end up in a funny state (e.g. rejecting some 
> actions which would otherwise be possible) after doing CSA until we 
> disconnect.

I'm not all that worried about that.

> > I guess I'd like to have the CSA stuff addressed, but it seems we
> > haven't really closed on the best way yet, and I don't want to hold off
> > your work for it for too long?
> 
> If you're okay with that then I'll just send out the [PATCH].

Sounds fine, thanks.

johannes