From: "Frank Schäfer" <fschaefer.oss@googlemail.com>
To: Luca Olivetti <luca@ventoso.org>, Fengguang Wu <fengguang.wu@intel.com>
Cc: Mauro Carvalho Chehab <m.chehab@samsung.com>,
linux-media@vger.kernel.org, Jet Chen <jet.chen@intel.com>,
Su Tao <tao.su@intel.com>, Yuanhan Liu <yuanhan.liu@intel.com>,
LKP <lkp@01.org>,
linux-kernel@vger.kernel.org, crope@iki.fi
Subject: Re: [media/dvb_usb_af9005] BUG: unable to handle kernel paging request (WAS: [media/em28xx] BUG: unable to handle kernel)
Date: Thu, 25 Sep 2014 15:54:05 +0200 [thread overview]
Message-ID: <54241E7D.3050201@googlemail.com> (raw)
In-Reply-To: <5421E00B.2050404@ventoso.org>
Am 23.09.2014 um 23:03 schrieb Luca Olivetti:
> El 23/09/14 20:52, Frank Schäfer ha escrit:
>
>>>> This seems to be an ancient bug, which is known at least since 5 1/2 years:
>>>> https://lkml.org/lkml/2009/2/4/350
> [...]
>>> #if defined(CONFIG_MODULE) || defined(CONFIG_DVB_USB_AF9005_REMOTE)
>> What happens, if CONFIG_MODULES is enabled, but neither module
>> af9005-remote nor any other IR module is available ?
>> Has this ever been tested ?
> I think I tested at the time and symbol_request returned NULL in that
> case, however I'm not sure and I cannot find any documentation on how
> symbol_request is supposed to work in that case.
Ok, thanks.
I assume noone wants to invest some time into this old driver and covert
it to todays kernel IR infrastructure as suggested by Antti ? :-)
Then I'm going to send a patch with the
#if defined(CONFIG_MODULE) || defined(CONFIG_DVB_USB_AF9005_REMOTE)
approach.
That's at least better than leaving the bug unfixed.
Regards,
Frank
next prev parent reply other threads:[~2014-09-25 13:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-19 1:41 [media/em28xx] BUG: unable to handle kernel Fengguang Wu
2014-09-19 19:01 ` Frank Schäfer
2014-09-19 19:22 ` [media/dvb_usb_af9005] BUG: unable to handle kernel paging request (WAS: [media/em28xx] BUG: unable to handle kernel) Frank Schäfer
2014-09-19 19:55 ` Luca Olivetti
2014-09-20 11:18 ` Antti Palosaari
2014-09-23 18:52 ` Frank Schäfer
2014-09-23 21:03 ` Luca Olivetti
2014-09-25 13:54 ` Frank Schäfer [this message]
2014-09-25 15:57 ` Luca Olivetti
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=54241E7D.3050201@googlemail.com \
--to=fschaefer.oss@googlemail.com \
--cc=crope@iki.fi \
--cc=fengguang.wu@intel.com \
--cc=jet.chen@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkp@01.org \
--cc=luca@ventoso.org \
--cc=m.chehab@samsung.com \
--cc=tao.su@intel.com \
--cc=yuanhan.liu@intel.com \
/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).