Given that, I'm surprised that nobody has added a warning that
prints when those two flags are both passed to request_irq().
The problems have been around for a long time, "tested" and known
to be broken. They'll never go away without nag messages nudging
developers to fix the problems.
That's the best solution for USB, given that IRQF_DISABLED isn't
going to do what it claims to do.
- Dave
--