Re: SET, CLR, ISSET in types.h for _KERNEL builds
- From: "Poul-Henning Kamp" <phk@xxxxxxxxxxxxxx>
- Date: Wed, 28 Jun 2006 20:29:06 +0000
In message <20060628150227.R75801@xxxxxxxxxxxxxxxxx>, "Andrew R. Reiter" writes
:
I apologize for top posting, but I lost the email that I think my
point/question pertains to.
Part of this seems to be for compatibility / merging from drivers of other
OSes, no? If I am wrong, ignore me :-). If this is the case, would it be
better to create some common other area for things of this nature so that
it suffices to allow builds, but does not infect other areas of our own
code base?
That's what I proposed too: #include <sys/netbsd_compat.h>
--
Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
phk@xxxxxxxxxxx | TCP/IP since RFC 956
FreeBSD committer | BSD since 4.3-tahoe
Never attribute to malice what can adequately be explained by incompetence.
_______________________________________________
freebsd-arch@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@xxxxxxxxxxx"
- References:
- Re: SET, CLR, ISSET in types.h for _KERNEL builds
- From: Andrew R. Reiter
- Re: SET, CLR, ISSET in types.h for _KERNEL builds
- Prev by Date: Re: SET, CLR, ISSET in types.h for _KERNEL builds
- Next by Date: Re: Accessing disks via their serial numbers.
- Previous by thread: Re: SET, CLR, ISSET in types.h for _KERNEL builds
- Next by thread: Re: SET, CLR, ISSET in types.h for _KERNEL builds
- Index(es):
Relevant Pages
|
