linux-kernel - Re: linux-next: sound tree build failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 02 Feb 2010 11:40:03 +0100
From:	Takashi Iwai <tiwai@...e.de>
To:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Samuel Ortiz <sameo@...ux.intel.com>
Subject: Re: linux-next: sound tree build failure

At Tue, 2 Feb 2010 10:31:12 +0000,
Mark Brown wrote:
> 
> On Tue, Feb 02, 2010 at 08:27:19AM +0100, Takashi Iwai wrote:
> 
> > Well, I don't think the codec register definitions don't have to be
> > dependent on mfd tree at all.  All other codec drivers have own
> > definitions.
> 
> > Mark, can it be self-contained?
> 
> No, it needs to look at things like the multi-function pin configuration
> in order to configure itself correctly.

Hm, then shouldn't it depend on mfd?



Takashi
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/