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 10:56:45 -0400 (EDT) [thread overview]
Message-ID: <alpine.LFD.2.20.1605271046310.18077@localhost.localdomain> (raw)
In-Reply-To: <87twhjk66y.fsf@nemi.mork.no>
On Fri, 27 May 2016, Bj?rn Mork wrote:
> "Robert P. J. Day" <rpjday@crashcourse.ca> writes:
>
> > while i'm here, some pedantry ... what is the point of adding a
> > header file somewhere under include/uapi/<somedir> 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
========================================================================
next prev parent reply other threads:[~2016-05-27 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 12:07 exporting kernel headers via the include/uapi directory Robert P. J. Day
2016-05-27 12:33 ` Robert P. J. Day
2016-05-27 12:59 ` Bjørn Mork
2016-05-27 14:56 ` Robert P. J. Day [this message]
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.1605271046310.18077@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).