From: Tomek The Messenger <tomekthemessenger@gmail.com>
To: kernelnewbies@kernelnewbies.org
Subject: Writing framework in kernel
Date: Sun, 22 Mar 2020 17:08:15 +0100 [thread overview]
Message-ID: <CAA4NGysHmQoN5Uz87LbssNSh6PD+rp1+j62ttcUMFq3ZhfOsuQ@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1257 bytes --]
Hi
I am writing some framework for my kernel drivers. I delegated to framework
the code which is common amongs all kernel drivers. So my framework module
core.c has none probe, remove functions. It has also none module_init,
module_exit functions at those are not needed.
1.) When I do modprobe of my core.ko I got error:
15.092976] testframework_core: module license 'unspecified' taints kernel.
[ 15.129532] testframework_core : Unknown symbol regmap_write (err 0)
[ 15.129554] testframework_core : Unknown symbol devm_kmalloc (err 0)
[ 15.129573] rstctl_core testframework_core : Unknown symbol
of_property_read_variable_u32_array (err 0)
[ 15.129598] testframework_core : Unknown symbol sysfs_remove_groups (err
0)
etc
So I suppose I need to put in my core.c line:
MODULE_LICENSE("GPL v2");
at the end of file in order to get rid of above problems. I will check if
it helps.
However when I am looking at build-in frameworks in linux kernel nobody put
line:
MODULE_LICENSE("GPL v2");
So why I have to and for example here:
https://elixir.bootlin.com/linux/latest/source/drivers/reset/core.c
there is none such line and everything works?
This is what I completely don't understand. My framework is external
module, maybe this is the reason???
[-- Attachment #1.2: Type: text/html, Size: 1612 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next reply other threads:[~2020-03-22 16:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-22 16:08 Tomek The Messenger [this message]
2020-03-22 16:37 ` Writing framework in kernel Greg KH
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=CAA4NGysHmQoN5Uz87LbssNSh6PD+rp1+j62ttcUMFq3ZhfOsuQ@mail.gmail.com \
--to=tomekthemessenger@gmail.com \
--cc=kernelnewbies@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).