From: "Arnd Bergmann" <arnd@arndb.de>
To: "Mike Isely at pobox" <isely@pobox.com>,
"Arnd Bergmann" <arnd@kernel.org>
Cc: "Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Lecopzer Chen" <lecopzer.chen@mediatek.com>,
"Hans Verkuil" <hverkuil-cisco@xs4all.nl>,
"Łukasz Stelmach" <l.stelmach@samsung.com>,
"laurent.pinchart" <laurent.pinchart@ideasonboard.com>,
"Jacopo Mondi" <jacopo@jmondi.org>,
"Andrzej Pietrasiewicz" <andrzejtp2010@gmail.com>,
linux-media@vger.kernel.org,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] media: pvrusb2: fix DVB_CORE dependency
Date: Wed, 18 Jan 2023 16:57:19 +0100 [thread overview]
Message-ID: <2f310818-7b19-4c07-9948-d5e413989594@app.fastmail.com> (raw)
In-Reply-To: <f045d0c6-0043-8feb-a423-954ce381396d@isely.net>
On Wed, Jan 18, 2023, at 16:39, Mike Isely wrote:
> That doesn't seem right. The pvrusb2 module should reference that
> symbol like any other. There is no special treatment of it within
> pvrusb2 - so why is that requiring special treatment here?
The problem is that VIDEO_PVRUSB2_DVB is a 'bool' symbol, not
a 'tristate', so the existing 'depends on DVB_CORE' is not sufficient.
Another way to do this would be to prevent VIDEO_PVRUSB2 from
being built-in when DVB_CORE is a module:
config VIDEO_PVRUSB2
tristate "Hauppauge WinTV-PVR USB2 support"
depends on VIDEO_DEV && I2C
+ depends on DVB_CORE || !DVB_CORE
select VIDEO_TUNER
select VIDEO_TVEEPROM
select VIDEO_CX2341X
but that doesn't feel right for users that don't care about DVB
support.
> Is it possible that dvb_module_probe and dvb_module_release are not
> exported? (Or that there are two corresponding different exported
> symbol names that pvrusb2 should be using instead?)
No.
Arnd
prev parent reply other threads:[~2023-01-18 16:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-17 17:10 Arnd Bergmann
2023-01-18 15:39 ` Mike Isely
2023-01-18 15:57 ` Arnd Bergmann [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=2f310818-7b19-4c07-9948-d5e413989594@app.fastmail.com \
--to=arnd@arndb.de \
--cc=andrzejtp2010@gmail.com \
--cc=arnd@kernel.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=isely@pobox.com \
--cc=jacopo@jmondi.org \
--cc=l.stelmach@samsung.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=lecopzer.chen@mediatek.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@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
all inboxes | Powered by JetHome®