From: Jean Delvare <khali@linux-fr.org>
To: Mauro Carvalho Chehab <mchehab@brturbo.com.br>,
Linus Torvalds <torvalds@osdl.org>
Cc: Ricardo Cerqueira <v4l@cerqueira.org>,
linux-kernel@vger.kernel.org, video4linux-list@redhat.com,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: Recursive dependency for SAA7134 in 2.6.15-rc7
Date: Wed, 28 Dec 2005 21:02:57 +0100 [thread overview]
Message-ID: <20051228210257.16c7a647.khali@linux-fr.org> (raw)
In-Reply-To: <1135726855.6709.4.camel@localhost>
Hi Mauro, Linus,
> > I gave a try to 2.6.15-rc7 and "make menuconfig" tells me:
> > Warning! Found recursive dependency: VIDEO_SAA7134_ALSA VIDEO_SAA7134_OSS VIDEO_SAA7134_ALSA
> >
> > This seems to be the consequence of this patch:
> > http://www.kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=7bb9529602f8bb41a92275825b808a42ed33e5be
> >
> > How do we fix that? menuconfig is indeed really confused by the current
> > setup. I have the following patch which makes it happier:
>
> Please test this patch. It seems that provides the same behavior with a
> non-recursive logic.
Looks good to me, except for the coding style. Also, depending on both
SND and SOUND doesn't make much sense, as SND itself already depends on
SOUND, so we can simplify the SAA7134_ALSA dependency list.
Linus, can you please apply this patch before releasing 2.6.15?
Thanks.
Fix the cyclic dependency issue between CONFIG_SAA7134_ALSA and
CONFIG_SAA7134_OSS (credits to Mauro Carvalho Chehab.)
Signed-off-by: Jean Delvare <khali@linux-fr.org>
---
drivers/media/video/saa7134/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-2.6.15-rc7.orig/drivers/media/video/saa7134/Kconfig 2005-12-28 19:13:38.000000000 +0100
+++ linux-2.6.15-rc7/drivers/media/video/saa7134/Kconfig 2005-12-28 20:50:37.000000000 +0100
@@ -14,7 +14,7 @@
config VIDEO_SAA7134_ALSA
tristate "Philips SAA7134 DMA audio support"
- depends on VIDEO_SAA7134 && SOUND && SND && (!VIDEO_SAA7134_OSS || VIDEO_SAA7134_OSS = m)
+ depends on VIDEO_SAA7134 && SND
select SND_PCM_OSS
---help---
This is a video4linux driver for direct (DMA) audio in
@@ -25,7 +25,7 @@
config VIDEO_SAA7134_OSS
tristate "Philips SAA7134 DMA audio support (OSS, DEPRECATED)"
- depends on VIDEO_SAA7134 && SOUND_PRIME && (!VIDEO_SAA7134_ALSA || VIDEO_SAA7134_ALSA = m)
+ depends on VIDEO_SAA7134 && SOUND_PRIME && (!VIDEO_SAA7134_ALSA || (VIDEO_SAA7134_ALSA=m && m))
---help---
This is a video4linux driver for direct (DMA) audio in
Philips SAA713x based TV cards using OSS
--
Jean Delvare
next prev parent reply other threads:[~2005-12-28 19:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 20:53 Recursive dependency for SAA7134 in 2.6.15-rc7 Jean Delvare
2005-12-27 23:40 ` Mauro Carvalho Chehab
2005-12-28 20:02 ` Jean Delvare [this message]
2005-12-28 20:10 ` Mauro Carvalho Chehab
2005-12-29 20:00 ` Roman Zippel
2005-12-29 20:13 ` Jean Delvare
2005-12-29 20:19 ` Roman Zippel
2005-12-29 21:07 ` Jean Delvare
2005-12-30 10:01 ` Mauro Carvalho Chehab
2005-12-30 11:06 ` Jean Delvare
2005-12-30 13:39 ` Mauro Carvalho Chehab
2005-12-31 18:39 ` Jean Delvare
2006-01-05 4:15 ` Roman Zippel
2006-01-05 8:28 ` Jean Delvare
2005-12-29 3:20 ` Roman Zippel
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=20051228210257.16c7a647.khali@linux-fr.org \
--to=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@brturbo.com.br \
--cc=torvalds@osdl.org \
--cc=v4l@cerqueira.org \
--cc=video4linux-list@redhat.com \
--cc=zippel@linux-m68k.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