[alsa-devel] wrong print debugging message code

[Mark Brown]

On Mon, Jun 23, 2008 at 02:13:19PM +0200, Takashi Iwai wrote:

> It depends on your plan.  Definitely nice to fix it for 2.6.27,
> though.

I've actually just written a patch ripping them all out (I'd probably
have submitted it already if I hadn't been reviewing Ben's changes) -
turns out that none of the drivers were actually using their dbg()
macros anyway so it won't have any runtime effect, though obviously a
fix would still be good.