From: danielhilst@gmail.com (Daniel.)
To: kernelnewbies@lists.kernelnewbies.org
Subject: make headers_install for out-of-tree modules
Date: Thu, 8 Oct 2015 17:48:58 -0300 [thread overview]
Message-ID: <CAF3SDA5spY-Oq4h6pC7DTmhNApLtjLN+yoKB1d591FtimP0qrg@mail.gmail.com> (raw)
In-Reply-To: <20151007160910.GA9669@kroah.com>
Hi,
thanks for the replies
Well, I'm using out-of-tree for development, I use it in one tree
while working and on another at home, so I keep my module out-of-tree
at only one repository, and compile against too trees. This is my
header[1], it doesn't have anything special, only ioctl definitions. I
read that this header processing is mainly because of libc and
syscalls integration. Since I don't mess with syscalls and libc stuff
do I need to process them too? When and why this header processing
applies?
[1] https://bitbucket.org/danielhilst/nrf24/src/1b63724a4bcf181568a0970133d1e51a5883ad9f/include/linux/nrf24.h?at=master&fileviewer=file-view-default
Best regards,
2015-10-07 13:09 GMT-03:00 Greg KH <greg@kroah.com>:
> On Wed, Oct 07, 2015 at 10:51:25AM -0300, Daniel. wrote:
>> Uhh, as I see from docs, this isn't supported,
>>
>> --- 2.3 Targets
>>
>> When building an external module, only a subset of the "make"
>> targets are available.
>> >From https://www.kernel.org/doc/Documentation/kbuild/modules.txt
>>
>> So, how can I export ioctl calls defined by an out-of-tree module?
>
> You get your out-of-tree module merged into the tree and it's
> automatically solved for you :)
--
"Do or do not. There is no try"
Yoda Master
prev parent reply other threads:[~2015-10-08 20:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-07 13:46 make headers_install for out-of-tree modules Daniel.
2015-10-07 13:51 ` Daniel.
2015-10-07 15:09 ` Yann Droneaud
2015-10-07 16:09 ` Greg KH
2015-10-08 20:48 ` Daniel. [this message]
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=CAF3SDA5spY-Oq4h6pC7DTmhNApLtjLN+yoKB1d591FtimP0qrg@mail.gmail.com \
--to=danielhilst@gmail.com \
--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).