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/1b63724a4bcf181568a0970133d1e51a... 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