--- On Sun, 25/9/11, Mauro Carvalho Chehab <[email protected]> wrote:
> Ok, I've applied it, but it doesn't sound a good idea to me
> to do:
> 
> +    mutex_unlock(&dev->lock);
>      em28xx_init_extension(dev);
> +    mutex_lock(&dev->lock);
> 

Yes, I suppose it's the logical equivalent of moving the 
em28xx_init_extension(dev) call from em28xx_init_dev(), and placing it 
immediately after the final mutex_unlock(&dev->lock) call in em28xx_usb_probe() 
instead. Which would be cleaner, quite frankly.

Which stage of the v4l2 initialisation triggers the race with udev? 
v4l2_device_register()? 

Cheers,
Chris

--
To unsubscribe from this list: send the line "unsubscribe linux-media" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to