On Tue, 15 Feb 2005, Randy.Dunlap wrote:
>
> In 2.6.11-rc4, any idea what these mean, what causes them?
> They are all kcalloc() calls.
Tends to imply that something wasn't declared, or was declared with no
explicit type. Alternatively, it was parsed as a call, but type
evaluation failed for the call for some other reason (maybe the arguments
couldn't be evaluated).
If it wasn't declared (or some other error happened during evaluation),
you should see a warning about undefined symbol too. Strange.
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
