On Sun, Feb 2, 2014 at 12:38 AM, Josh Triplett <josh@xxxxxxxxxxxxxxxx> wrote: > I'd suggest that either it should have exactly the same behavior as it does > when applied to the type of a function argument (suppressing > Sparse-specific pointer qualifier mismatches on input), or it should be > prohibited entirely on standalone variable declarations. I'd be fine > with the latter, if you prefer. BTW, patch are welcome to make it consistent, hopefully in a not too complicate way. Chris -- To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
