linux-kernel - Re: linux-next: build failure after merge of the sound-asoc tree

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] [day] [month] [year] [list]

Message-ID: <20120625090340.GD4037@opensource.wolfsonmicro.com>
Date:	Mon, 25 Jun 2012 10:03:40 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	Rajeev kumar <rajeev-dlh.kumar@...com>
Cc:	Stephen Rothwell <sfr@...b.auug.org.au>,
	Liam Girdwood <lrg@...com>,
	"linux-next@...r.kernel.org" <linux-next@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the sound-asoc tree

On Mon, Jun 25, 2012 at 11:39:30AM +0530, Rajeev kumar wrote:

> 3. We can pick the patches circulated by Viresh Kumar where we don't
> have HAVE_CLK defined for x86_64, then the inline routines like
> following should come into play:

This is what *should* be happening, in conjunction with architectures
doing the trivial work required to turn the clock API on now that there
is a generic clock API, but both of these things seem to be going
nowhere.  I've applied a bodge until someone decides it's worth applying
the stubs.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)