From: rpjday@crashcourse.ca (Robert P. J. Day)
To: kernelnewbies@lists.kernelnewbies.org
Subject: exporting kernel headers via the include/uapi directory
Date: Fri, 27 May 2016 08:07:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1605270758030.22693@localhost.localdomain> (raw)
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/<somedir> 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
========================================================================
next reply other threads:[~2016-05-27 12:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 12:07 Robert P. J. Day [this message]
2016-05-27 12:33 ` exporting kernel headers via the include/uapi directory Robert P. J. Day
2016-05-27 12:59 ` Bjørn Mork
2016-05-27 14:56 ` Robert P. J. Day
2016-05-27 16:14 ` Greg KH
2016-05-27 16:25 ` Robert P. J. Day
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LFD.2.20.1605270758030.22693@localhost.localdomain \
--to=rpjday@crashcourse.ca \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).