On Sun, 25 Nov 2001 18:09:05 -0800,
"H. Peter Anvin" <hpa@zytor.com> wrote:
>Keith Owens wrote:
>> bonding.c includes limits.h, picked up from gcc, OK.
>> limits.h includes syslimits.h from gcc, OK.
>> syslimits.h tries to include_next <limits.h> to get the user space
>> limits, not OK.
>>
>> Any kernel code that includes limits.h or syslimits.h is polluted by
>> user space headers. net/bonding.c does not even need limits.h.
>
>How UTTERLY braindamaged... I guess we could provide a (dummy?)
><limits.h> for the kernel environment. I would definitely like to see
>the standard compiler-related headers like <stdint.h> as well...
We already have include/linux/limits.h that is included by filesystem
code. If anybody needs additional #defines, they can go in our version
of limits.h instead of trying to use the gcc version.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Nov 30 2001 - 21:00:20 EST