From: David Miller <[email protected]>
Date: Tue, 30 Oct 2007 14:59:26 -0700 (PDT)
> I think the thing to do is just __KERNEL__ protect the
> <linux/string.h> include and require userspace to
> include <string.h> itself when using these headers.
>
> That's what I'm testing right now.
>
> I'm pretty sure those inlines are indeed used by userspace.
Actually, I'm tempted to put <string.h> in the ifndef __KERNEL__
block of that header.
That's ugly.
An alternative is to add linux/string.h to unifdef-y and have it
include <string.h> when !__KERNEL__ in order to handle cases like
this.
Sam, what do you think of that idea?
-
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/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
