Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932917Ab2JWJwl (ORCPT ); Tue, 23 Oct 2012 05:52:41 -0400 Received: from mail.skyhub.de ([78.46.96.112]:35765 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932858Ab2JWJwi (ORCPT ); Tue, 23 Oct 2012 05:52:38 -0400 Date: Tue, 23 Oct 2012 11:52:34 +0200 From: Borislav Petkov To: Tang Chen Cc: tony.luck@intel.com, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, miaox@cn.fujitsu.com, laijs@cn.fujitsu.com, wency@cn.fujitsu.com, x86@kernel.org, linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] Replace if statement with WARN_ON_ONCE() in cmci_rediscover(). Message-ID: <20121023095234.GA22715@liondog.tnic> Mail-Followup-To: Borislav Petkov , Tang Chen , tony.luck@intel.com, tglx@linutronix.de, mingo@redhat.com, hpa@zytor.com, miaox@cn.fujitsu.com, laijs@cn.fujitsu.com, wency@cn.fujitsu.com, x86@kernel.org, linux-edac@vger.kernel.org, linux-kernel@vger.kernel.org References: <1350625528-1385-1-git-send-email-tangchen@cn.fujitsu.com> <1350625528-1385-2-git-send-email-tangchen@cn.fujitsu.com> <20121019164045.GE11958@aftab.osrc.amd.com> <5084AB10.7010807@cn.fujitsu.com> <20121022101442.GB8352@liondog.tnic> <50860711.10807@cn.fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <50860711.10807@cn.fujitsu.com> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 608 Lines: 21 On Tue, Oct 23, 2012 at 10:55:13AM +0800, Tang Chen wrote: > So, how about warn once, and continue: > if (cpu == dying) { > WARN_ON_ONCE(cpu == dying); > continue; > } > > or, use BUG_ON() instead ? Let me ask you again, but I want you to think real hard this time: "Why do we need to warn? What good would that bring us?" -- Regards/Gruss, Boris. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/