On Wed, 2014-11-19 at 19:47 +0100, Felix Fietkau wrote: > >> + * This function may not be called in IRQ context. Calls to this function > >> + * for a single hardware must be synchronized against each other. Calls > >> + * to this function, ieee80211_tx_status_ni() and ieee80211_tx_status_irqsafe() > >> + * may not be mixed for a single hardware. Must not run concurrently with > >> + * ieee80211_rx() or ieee80211_rx_ni(). > > > > None of that seems very likely. Did you just copy/paste it? :) > Yes, I copy/pasted it. I wasn't sure if these requirements would be > necessary for the no-skb status as well, just figured it'd be safe to > leave them in. I think if you move the eosp() that leaves you pretty much with only things that are safe? johannes -- 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
