From: Linus Walleij <linus.walleij@linaro.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Cameron <jic23@kernel.org>,
linux-iio@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: iio/accel/kxsd9_i2c: no license, taints kernel
Date: Mon, 13 Nov 2017 11:22:36 +0100 [thread overview]
Message-ID: <CACRpkdb_101_guBu2dC5c+avJHFnFSw4fc7Ug7+B8tAuqz=UeQ@mail.gmail.com> (raw)
In-Reply-To: <a21be947-5c1f-eb71-83ad-63222b46c499@infradead.org>
On Sat, Nov 11, 2017 at 8:21 PM, Randy Dunlap <rdunlap@infradead.org> wrote:
> On 11/11/17 10:53, Randy Dunlap wrote:
>> [44583.951806] kxsd9_i2c: module license 'unspecified' taints kernel.
>> [44583.951931] kxsd9_i2c: Unknown symbol __devm_regmap_init_i2c (err 0)
>>
>> __devm_regmap_i2c() is EXPORT_SYMBOL_GPL(), so a non-compatible license
>> cannot use it.
>>
>
>
> and iio/adc/qcom-vadc-common.c:
>
> qcom_vadc_common: module license 'unspecified' taints kernel.
I wrote these, I will send a patch.
Yours,
Linus Walleij
prev parent reply other threads:[~2017-11-13 10:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-11 18:53 iio/accel/kxsd9_i2c: no license, taints kernel Randy Dunlap
2017-11-11 19:21 ` Randy Dunlap
2017-11-13 10:22 ` Linus Walleij [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='CACRpkdb_101_guBu2dC5c+avJHFnFSw4fc7Ug7+B8tAuqz=UeQ@mail.gmail.com' \
--to=linus.walleij@linaro.org \
--cc=jic23@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.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).