From: Randy Dunlap <rdunlap@xenotime•net>
To: Stephen Rothwell <sfr@canb•auug.org.au>
Cc: linux-next@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>,
Greg KH <gregkh@suse•de>,
alsa-devel@alsa-project•org
Subject: Re: linux-next: Tree for Jan 9 (sound/soc vs. drivers/misc)
Date: Mon, 09 Jan 2012 12:57:04 -0800 [thread overview]
Message-ID: <4F0B54A0.20905@xenotime.net> (raw)
In-Reply-To: <20120109170457.4465dfc66a0eace4a2230fef@canb.auug.org.au>
On 01/08/2012 10:04 PM, Stephen Rothwell wrote:
> Hi all,
>
> Changes since 20120106:
>
> This tree is still broken for sparc64 defconfig (at least).
AFAICT, all builds (on X86_32 or X86_64) have this kconfig warning:
drivers/misc/Kconfig:212:error: recursive dependency detected!
drivers/misc/Kconfig:212: symbol ATMEL_SSC is selected by SND_ATMEL_SOC_SSC
sound/soc/atmel/Kconfig:9: symbol SND_ATMEL_SOC_SSC is selected by SND_AT91_SOC_SAM9G20_WM8731
sound/soc/atmel/Kconfig:18: symbol SND_AT91_SOC_SAM9G20_WM8731 depends on ATMEL_SSC
--
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2012-01-09 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 6:04 linux-next: Tree for Jan 9 Stephen Rothwell
2012-01-09 20:50 ` linux-next: Tree for Jan 9 (net/core/sock.c) Randy Dunlap
2012-01-09 21:44 ` David Miller
2012-01-09 20:57 ` Randy Dunlap [this message]
2012-01-09 21:05 ` linux-next: Tree for Jan 9 (arch/x86/pci/amd_bus.c) Randy Dunlap
2012-01-09 22:40 ` Bjorn Helgaas
2012-01-10 20:57 ` Randy Dunlap
2012-01-09 21:14 ` linux-next: Tree for Jan 9 (irqdomain.c) Randy Dunlap
2012-01-15 16:37 ` Sebastian Andrzej Siewior
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=4F0B54A0.20905@xenotime.net \
--to=rdunlap@xenotime$(echo .)net \
--cc=alsa-devel@alsa-project$(echo .)org \
--cc=gregkh@suse$(echo .)de \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.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