Messages in this thread | | | Subject | Re: [RFC] Splitting kernel headers and deprecating __KERNEL__ | From | Arjan van de Ven <> | Date | Sun, 28 Nov 2004 08:13:39 +0100 |
| |
> The problem with these (atomic.h
that is a very non portable header and there are several good alternatives (see the apr library for example). In fact. atomic.h is *dangerous* in userspace, it is only atomic if CONFIG_SMP is set, so if you compile your app on a machine without that set and then run it on an smp machine, you are not atomic.
> > , bitops.h
again not portable
> > , byteorder.h,
there are perfectly good alternatives in glibc
> > div64.h,
huh? what is wrong with "/" in C
> list.h
this one I can see
> > , spinlock.h
EHHHH????? Spinlocks in userland? You got to be kidding.
> , unaligned.h
weird
> and xor.h)
xor.h is very raid specific (and GPL with lots of code, so a license trap)
- 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/
| |