Hi,
In spite of the patches I have been sending (and resending!) over the
past months, there are still 118 occurrences of the idle IRQF_DISABLED
flag in the kernel code. This corresponds to 31 patches which haven't
been accepted yet.
What would you advise to get rid of IRQF_DISABLED for good?
* Send a treewide patch removing the last occurrences in one shot,
bypassing the regular maintainers? Who could take it?
* Remove the definition of IRQF_DISABLED to force the individual
maintainers (and out of tree drivers!) to update their code? It
could be a way of seeing which code isn't maintained any more ;)
* Continue to resend the patches for a few more cycles, until the
corresponding maintainers can no longer bear the discredit?
* Any other solution?
Thank you in advance for your advise!
Michael.
--
Michael Opdenacker, CEO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
+33 484 258 098
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
