On Fri, 25 May 2007, Al Viro wrote:
>
> What did you want that check in evaluate_compare() to catch? Is that
> about warning on explicit comparison with NULL?
Yes. It was explicitly meant to be a "anybody who tests this pointer
missed the 'safe' part of it".
But I never used it, so it was really meant as a concept thing, and I
don't think it's wrong to test against non-null.
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
