> > + /* if no one will get it anyway, don't even allocate it. > > + * unlikely because this is only relevant for APs > > + * where the device must be open... */ > > + if (unlikely(!local->apdev)) > > + return; > > Why not just let it Oops and show the bug? In what cases is it ok > for apdev to not be set?
> Can we get whitespace changes like this in a separate patch? Sure. I'll just remove it from this patch for now. > again, so should we just let the Oops happen? I'm thinking there might be race conditions where userspace does something, then drops the ap device but after that some operations complete and would lead to the oops too. Wasn't really sure. johannes
signature.asc
Description: This is a digitally signed message part
