From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Perches Subject: Re: [PATCH 00/12] scsi/NCR5380: fix debugging macros and #include structure Date: Tue, 18 Mar 2014 06:07:31 -0700 Message-ID: <1395148051.2812.51.camel@joe-AO722> References: <20140318002822.372705594@telegraphics.com.au> <1395112756.20860.1.camel@joe-AO722> <1395146702.2812.47.camel@joe-AO722> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=m.gmane.org@lists.infradead.org To: Geert Uytterhoeven Cc: Sam Creasey , Linux/m68k , Russell King , scsi , Michael Schmitz , "linux-kernel@vger.kernel.org" , "James E.J. Bottomley" , Finn Thain , "linux-arm-kernel@lists.infradead.org" List-Id: linux-m68k@vger.kernel.org On Tue, 2014-03-18 at 13:55 +0100, Geert Uytterhoeven wrote: > On Tue, Mar 18, 2014 at 1:45 PM, Joe Perches wrote: Hi Geert. > > #define dprintk(flg, fmt, ...) \ > > do { if (0) pr_debug(fmt, ##__VA_ARGS__); } while (0) > > Na, no_printk(): > > #define dprintk(flg, fmt, ...) no_printk(fmt, ##__VA_ARGS__) Fine, but with a correction. no_printk keeps all side effects like performing any function calls made by the statement or accessing any volatiles. Using do { if (0) no_printk(fmt, ##__VA_ARGS__); } while (0) does not have any side-effects.