Re: exporting kernel headers via the include/uapi directory
On Fri, 27 May 2016, Greg KH wrote: > On Fri, May 27, 2016 at 08:07:17AM -0400, Robert P. J. Day wrote: > > > > next question about exporting kernel headers, this one related to > > the content placed under include/uapi/. > > > > is there any rationale for header files to be living under > > include/uapi/ if they're not listed in the corresponding > > Kbuild file for export? > > > > for example, in include/uapi/drm, there are 24 header files, but > > only 21 of them are mentioned in that Kbuild file -- the Kbuild file > > doesn't mention armada_drm.h, etnaviv_drm.h or omap_drm.h, and i've > > verified that running "make headers_install" doesn't install those > > three headers. > > > > i'm going to assume those are just forgotten remnants or something, > > unless there is some actual reason to do that. is there? > > Why not ask this on the drm mailing list? because drm is not the only subdirectory for which that's true, and the question really is a generic one. 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 http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: exporting kernel headers via the include/uapi directory
On Fri, May 27, 2016 at 08:07:17AM -0400, Robert P. J. Day wrote: > > next question about exporting kernel headers, this one related to > the content placed under include/uapi/. > > is there any rationale for header files to be living under > include/uapi/ if they're not listed in the corresponding > Kbuild file for export? > > for example, in include/uapi/drm, there are 24 header files, but > only 21 of them are mentioned in that Kbuild file -- the Kbuild file > doesn't mention armada_drm.h, etnaviv_drm.h or omap_drm.h, and i've > verified that running "make headers_install" doesn't install those > three headers. > > i'm going to assume those are just forgotten remnants or something, > unless there is some actual reason to do that. is there? Why not ask this on the drm mailing list? ___ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: exporting kernel headers via the include/uapi directory
On Fri, 27 May 2016, Bjørn Mork wrote: > "Robert P. J. Day"writes: > > > while i'm here, some pedantry ... what is the point of adding a > > header file somewhere under include/uapi/ without > > *immediately* adding it to the Kbuild file so that it's exported? > > I don't know the answer to that. But having done this once, I can > answer why *I* did it: Ignorance. > > I didn't realize that I had to update the Kbuild file, but wrongly > assumed that creating a file somewhere in include/uapi was enough. > Maybe that's the reason for most of these errors? Some automatic > check, or maybe even automatic fix, would be nice. Should be pretty > easy to do. unless there really is some reason to not do those two things at the same time, but for the life of me, i can't imagine what it is. 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 http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Re: exporting kernel headers via the include/uapi directory
On Fri, 27 May 2016, Robert P. J. Day wrote: > next question about exporting kernel headers, this one related to > the content placed under include/uapi/. > > is there any rationale for header files to be living under > include/uapi/ if they're not listed in the corresponding > Kbuild file for export? > > for example, in include/uapi/drm, there are 24 header files, but > only 21 of them are mentioned in that Kbuild file -- the Kbuild file > doesn't mention armada_drm.h, etnaviv_drm.h or omap_drm.h, and i've > verified that running "make headers_install" doesn't install those > three headers. > > i'm going to assume those are just forgotten remnants or > something, unless there is some actual reason to do that. is there? while i'm here, some pedantry ... what is the point of adding a header file somewhere under include/uapi/ without *immediately* adding it to the Kbuild file so that it's exported? for example, i note that include/uapi/drm/amdgpu_drm.h was committed back in april of 2015, but a "headers-y" line for it wasn't added until nov of that same year. so what was that header file doing all that time in between? or is there some mechanism that allows export of UAPI header files even if they're not mentioned in Kbuild? 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 http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
exporting kernel headers via the include/uapi directory
next question about exporting kernel headers, this one related to the content placed under include/uapi/. is there any rationale for header files to be living under include/uapi/ if they're not listed in the corresponding Kbuild file for export? for example, in include/uapi/drm, there are 24 header files, but only 21 of them are mentioned in that Kbuild file -- the Kbuild file doesn't mention armada_drm.h, etnaviv_drm.h or omap_drm.h, and i've verified that running "make headers_install" doesn't install those three headers. i'm going to assume those are just forgotten remnants or something, unless there is some actual reason to do that. is there? 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 http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies