From: Manuel Lauss <manuel.lauss@googlemail•com>
To: Ralf Baechle <ralf@linux-mips•org>
Cc: alsa-devel@vger•kernel.org,
Stephen Rothwell <sfr@canb•auug.org.au>,
linux-next@vger•kernel.org,
Manuel Lauss <manuel.lauss@googlemail•com>
Subject: [PATCH] MIPS/sound: DB1200 audio support depends on MIPS arch.
Date: Thu, 10 Nov 2011 12:20:59 +0100 [thread overview]
Message-ID: <1320924059-4142-1-git-send-email-manuel.lauss@googlemail.com> (raw)
In-Reply-To: <20111110122241.eed1e785e4c015a51b9ef585@canb.auug.org.au>
DB1200 audio support should only be visible if MIPS/Alchemy arch is
selected. Fixes an x86-allmodconfig build failure in linux-next.
Reported-by: Stephen Rothwell <sfr@canb•auug.org.au>
Signed-off-by: Manuel Lauss <manuel.lauss@googlemail•com>
---
sound/soc/au1x/Kconfig | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/sound/soc/au1x/Kconfig b/sound/soc/au1x/Kconfig
index c620cbf9..a561040 100644
--- a/sound/soc/au1x/Kconfig
+++ b/sound/soc/au1x/Kconfig
@@ -52,7 +52,7 @@ config SND_SOC_DB1000
config SND_SOC_DB1200
tristate "DB1200/DB1300/DB1550 Audio support"
- select SND_SOC_AU1XPSC
+ depends on SND_SOC_AU1XPSC
select SND_SOC_AU1XPSC_AC97
select SND_SOC_AC97_CODEC
select SND_SOC_WM9712
--
1.7.7.2
next prev parent reply other threads:[~2011-11-10 11:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-10 1:22 linux-next: build failure after merge of the mips tree Stephen Rothwell
2011-11-10 11:20 ` Manuel Lauss [this message]
2011-11-10 11:34 ` [alsa-devel] [PATCH] MIPS/sound: DB1200 audio support depends on MIPS arch Mark Brown
2011-11-10 11:36 ` Mark Brown
2011-11-10 11:46 ` Manuel Lauss
2011-11-10 12:17 ` Ralf Baechle
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=1320924059-4142-1-git-send-email-manuel.lauss@googlemail.com \
--to=manuel.lauss@googlemail$(echo .)com \
--cc=alsa-devel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=ralf@linux-mips$(echo .)org \
--cc=sfr@canb$(echo .)auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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