From: Szymon Janc <szymon.janc@tieto.com>
To: Eugene Krasnikov <k.eugene.e@gmail.com>
Cc: "backports@vger.kernel.org" <backports@vger.kernel.org>,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: include/linux/device.h:715:38: error: 'THIS_MODULE' undeclared
Date: Thu, 11 Apr 2013 11:17:17 +0200 [thread overview]
Message-ID: <3231828.tgzQTMkMFI@uw000953> (raw)
In-Reply-To: <CAFSJ42a5PsnbhgEaWWWZTBDVKhKUGR4xWY1pEXPc-UaQcC9AFA@mail.gmail.com>
On Wednesday 10 of April 2013 17:21:57 Eugene Krasnikov wrote:
Hi,
> Thanx for reply. That also works.
> But is it a solution or workaround? May be there should be smarter
> check than just a kernel version?
Note that android kernel is not vanilla kernel.
If you have custom kernel (e.g android kernel) with extra features backported
you need to enable support for those features in compat-drivers for
your kernel i.e. mark it as applicable for lower kernel version (comparing to
vanilla kernel which introduced this feature)
The 'proper' solution would be to have support for Android (or CM) kernel in
compat-drivers (same as eg. RH kernel would). But Android kernels varies
heavily among devices and it could be hard to support all of them. It is also
worth noting that often custom non-mainlined code doesn't even build when
configured as module e.g. bluesleep driver from grouper kernel. This is extra
obstacle as one would have to fix or disable such offending code.
--
BR
Szymon Janc
prev parent reply other threads:[~2013-04-11 9:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 9:20 include/linux/device.h:715:38: error: 'THIS_MODULE' undeclared Eugene Krasnikov
2013-04-10 11:56 ` Szymon Janc
2013-04-10 14:21 ` Eugene Krasnikov
2013-04-11 9:17 ` Szymon Janc [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=3231828.tgzQTMkMFI@uw000953 \
--to=szymon.janc@tieto.com \
--cc=backports@vger.kernel.org \
--cc=k.eugene.e@gmail.com \
--cc=linux-wireless@vger.kernel.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