From mboxrd@z Thu Jan  1 00:00:00 1970
From: Takashi Iwai <tiwai@suse.de>
Subject: Re: wrong print debugging message code
Date: Mon, 23 Jun 2008 12:55:57 +0200
Message-ID: <s5habhc4dz6.wl%tiwai@suse.de>
References: <280b69ac0806202244s11e74363l4de3f020fed849be@mail.gmail.com>
Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka")
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mx1.suse.de (ns.suse.de [195.135.220.2])
	by alsa0.perex.cz (Postfix) with ESMTP id 082702440D
	for <alsa-devel@alsa-project.org>;
	Mon, 23 Jun 2008 12:55:58 +0200 (CEST)
In-Reply-To: <280b69ac0806202244s11e74363l4de3f020fed849be@mail.gmail.com>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
	<mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Sender: alsa-devel-bounces@alsa-project.org
Errors-To: alsa-devel-bounces@alsa-project.org
To: Jin-Young Park <mcjin02@gmail.com>
Cc: alsa-devel@alsa-project.org, Mark Brown <broonie@opensource.wolfsonmicro.com>
List-Id: alsa-devel@alsa-project.org

At Sat, 21 Jun 2008 14:44:47 +0900,
Jin-Young Park wrote:
> 
> Hello,
> 
> I written ASoC Audio driver for our company chip in linux kernel 2.6.24.1.
> New kernel 2.6.25.7 released before several days.
> So, I merge my ASoC Audio dirver to kernel 2.6.25.7.
> then I found wrong code that print debuuging message code in several files.
> These file location is kernel_src/sound/soc/codecs for SoC audio codec
> drvier files
> 
> These files include follow define code for print debug message.
> 
> ------------------------------------------------------------------------------------------------------------------------
> #define XXXX_DEBUG 0
> 
> #ifdef XXXX_DEBUG
> #define dbg(format, arg...) \
>         printk(KERN_DEBUG AUDIO_NAME ": " format "\n" , ## arg)
> #else
> #define dbg(format, arg...) do {} while (0)
> #endif
> ------------------------------------------------------------------------------------------------------------------------
> 
> I think "#ifdef XXXX_DEBUG" line is wrong. Because, XXXX_DEBUG was already
> defined 0.
> I known that "#ifdef" is only check defined or not defined, 0 or 1(false or
> true) are not check.
> "#if XXXX_DEBUG" code is more correct than "#ifdef XXXX_DEBUG".

#ifdef XXX_DEBUG is more common than #if XXX_DEBUG in the kernel
tree.  So, I'd suggest to keep #ifdef style.

The confusing thing is that it defines to '0' (and I'm not sure the
debug is activated as default in the current code -- Mark, Liam, is it
intentional?).

IMO, the debug should be basically off as default, and if enabled, it
should be defined to '1'.


Takashi