On Wed, 2 Jan 2002 13:23:32 -0800, Chris Wright <chrisat_private> wrote: >most drivers don't have a full include tree in their subdir. of course, >many don't even have their own subdir but share a subdir. i like being >able to keep the module code separated from the core kernel, but i'm not >sure what the preferred method is. keith, what do you recommend? Current practice allows either method, but selinux is the only code I know that requires a second symlink. AFAIK no other code has its own include/asm-$(ARCH) directory. This caused problems for kbuild 2.5 because of the support for separate source and object trees, but that is solved now. Other people are working on cleaning up the include files, to reduce complexity and interdependencies. They are probably the better people to talk to about merging with the main include files or staying separate. Other areas of the kernel like SCSI includes need cleaning up as well, it is better to agree on an overall design that fiddle with piecemeal changes. Leave it alone for now and consider it as part of the 2.5 clean up. _______________________________________________ linux-security-module mailing list linux-security-moduleat_private http://mail.wirex.com/mailman/listinfo/linux-security-module
This archive was generated by hypermail 2b30 : Wed Jan 02 2002 - 13:51:23 PST