Luis R. Rodriguez wrote:
The __nocast attribute is used to shut sparse up but we
don't need it, lets just use u16 directly.
Which warning does this remove?
The purpose of this system was (I think) to make it so that if you got
addr and value in the wrong order in calls to e.g. zd_ioread16() then
sparse would tell you about it. Looks like your patch would remove that
protection?
Admittedly it is a bit of a strange thing and no excuse for programmers
getting parameters in the wrong order.. if it needs to go then I'm happy
with whatever you decide.
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
