From: Randy Dunlap <rdunlap@xenotime.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-media@vger.kernel.org,
Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Ondrej Zary <linux@rainbow-software.org>,
Takashi Iwai <tiwai@suse.de>
Subject: Re: linux-next: Tree for Aug 5 (media/radio/radio-sf16fmr2)
Date: Fri, 5 Aug 2011 16:56:11 -0700 [thread overview]
Message-ID: <20110805165611.d2feaf32.rdunlap@xenotime.net> (raw)
In-Reply-To: <20110805143103.f9388ca143560d73caac60c1@canb.auug.org.au>
On Fri, 5 Aug 2011 14:31:03 +1000 Stephen Rothwell wrote:
> Hi all,
>
> [The kernel.org mirroring is running slowly today]
Is media/radio/radio-sf16fmr2 an ISA driver or a PCI driver?
ugh. Or is it an I2C driver?
linux-next fails with (this is not a new failure):
ERROR: "snd_tea575x_init" [drivers/media/radio/radio-sf16fmr2.ko] undefined!
ERROR: "snd_tea575x_exit" [drivers/media/radio/radio-sf16fmr2.ko] undefined!
The Kconfig entry for RADIO_SF16FMR2 is:
config RADIO_SF16FMR2
tristate "SF16FMR2 Radio"
depends on ISA && VIDEO_V4L2 && SND
and the Kconfig entry for SND_TEA575X is (not user visible):
config SND_TEA575X
tristate
depends on SND_FM801_TEA575X_BOOL || SND_ES1968_RADIO || RADIO_SF16FMR2
default SND_FM801 || SND_ES1968 || RADIO_SF16FMR2
This latter entry is in sound/pci/Kconfig and is under:
if SND_PCI
so it depends on PCI and SND_PCI.
This build fails when CONFIG_PCI is not enabled.
Suggestions?
thanks,
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-08-05 23:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-05 4:31 linux-next: Tree for Aug 5 Stephen Rothwell
2011-08-05 23:56 ` Randy Dunlap [this message]
2011-08-06 8:33 ` linux-next: Tree for Aug 5 (media/radio/radio-sf16fmr2) Takashi Iwai
2011-08-06 16:50 ` Randy Dunlap
2011-08-07 15:37 ` Takashi Iwai
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=20110805165611.d2feaf32.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=mchehab@infradead.org \
--cc=sfr@canb.auug.org.au \
--cc=tiwai@suse.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.