Re: should include/uapi include header files *unused* in kernel space?
On Sun, Jan 22, 2017 at 6:18 AM, Robert P. J. Daywrote: > > was perusing the UAPI content in the kernel source, prepping for a > course i'm teaching tomorrow, and just noticed there is a header file: > > $ find . -name mtd-user.h > ./include/uapi/mtd/mtd-user.h > $ > > which appears to be *entirely* unreferenced in the entire kernel code > base (outside of the Kbuild file that refers to it): > > $ grep -r 'mtd-user.h' * > include/uapi/mtd/Kbuild:header-y += mtd-user.h > $ Someone has a patch to remove msr-index.h which, in a similar way, only ended up being exported because of a Kbuild rule. So I'd imagine this file would be a candidate for a similar patch. https://lkml.org/lkml/2017/2/2/228. -- Jim ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
should include/uapi include header files *unused* in kernel space?
was perusing the UAPI content in the kernel source, prepping for a course i'm teaching tomorrow, and just noticed there is a header file: $ find . -name mtd-user.h ./include/uapi/mtd/mtd-user.h $ which appears to be *entirely* unreferenced in the entire kernel code base (outside of the Kbuild file that refers to it): $ grep -r 'mtd-user.h' * include/uapi/mtd/Kbuild:header-y += mtd-user.h $ does this make any sense? am i missing something here? i would have thought that if a header file includes content that is wholly used exclusively in user space, it would be part of a package like "mtd-devel", or something like that. is this just for convenience to keep all the mtd stuff in the same place? rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies