sparse is not to blame
Posted Oct 13, 2005 5:49 UTC (Thu) by proski
Parent article: Introducing gfp_t
It's important to note that the patch is not dictated by any shortcomings of sparse. No good code checker would like a function that takes enum as argument but passes it as int to other functions.
Also, the patch mostly replaces "unsigned int __nocast", which is sparse specific, with gfp_t, which is not (except that its definition uses __nocast in one header file).
to post comments)