On Tue, 30 Dec 2008, Sam Ravnborg wrote:
> Subject: [PATCH] kbuild: add checks for include of linux/types in userspace
> headers
> If we see __[us](8|16|32|64) then we must include <linux/types.h>
> + if ($line =~ m/__[us](8|16|32|64)\b/) {
> + printf STDERR "$filename:$lineno: " .
> + "found __[us]{8,16,32,64} type " .
> + "without #include <linux/types.h>\n";
> + $linux_types = 2;
> + # Warn until headers are all fixed
> + #$ret = 1;
> + }
FWIW, this also triggers on __[us]{8,16,32,64} in comments instead of in
actual code (just got caught ;-).
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
