After looking at the proposed solution, I personally find the suggestion for a serialization flag to be quite ridiculous. As others have mentioned, the mere presence of the flag means that driver writers will gloss over any concurrency issues that might exist in their driver on the mere assumption that specifying the serialization flag will handle it all for them. As the author of the most recent patches to radio-mr800, the proposed changes not only add additional complexity to the driver but also remove some of the fundamental error checking within the driver. Despite the fact the error check might not always be successful, it will still catch the majority of cases. I therefore NACK the proposed patches to this driver. The right thing to do is to actually correct the issue within all the drivers that need it. Is this a lot of work? Maybe, but it's a far better solution as each driver will be responsible for concurrency issues that it may or may not have. After all, wasn't this what the removal of the BKL was about in the first place? Regards, David Ellingsworth -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
