On Mon, Mar 26, 2007 at 02:59:39PM -0400, Russ Cox wrote: > No, you have it backward. > It is valid to pass void* to a const void* function. > It is *not* valid to pass const void* to a void* function. > > Right now __chk_user_ptr is a void* function, meaning > that all the places where it gets passed a const void* > are technically illegal -- gcc would warn about these, and > it is a (separate, as you observed) bug that sparse does not. > > The patch changes __chk_user_ptr to be a const void* > function, meaning that it will be legal to pass either void* > or const void* to it. This is the correct semantics. Hah, I see. Thanks for the explain. Ack. 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
