On Tuesday, June 11, 2013 09:24:28 PM Johannes Berg wrote: > On Tue, 2013-06-11 at 21:17 +0200, Thomas Hühn wrote: > > Hi Christian, > > > > I have not seen that patch in wireless-next, that's why I overlooked it... sorry. You are right and it's not in wireless-testing.git either. That's a bit odd. John, was this patch overlooked/lost or was there a problem with it? (Or: can you please put it into wireless-next) > > > carl9170 already supports the new rate control API (Patch from 2013-04-23). > > > <http://permalink.gmane.org/gmane.linux.kernel.wireless.general/107657> > > > > > > Can you please tell me what you think is missing? > > > > > > > You patch looks good to me. > > As I just saw an ath9k patch for rcu protection when ieee80211_get_tx_rates() is called. > > Should this be done in carl9170 as well ? > > I think that patch is wrong actually, probably should just do the rcu > protection inside the function. However the patch is completely wrong > anyway (C isn't python) so ... Uh, that's confusing. We are now talking about the patch from Thomas, right? If so: the previous "new rate control api" feature patch for carl9170 should be fine in this regard. Regards, Chr -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
