From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH] arch: configuration, deleting 'CONFIG_BUG' since always need it. Date: Tue, 28 May 2013 09:06:48 -0700 Message-ID: <51A4D618.3080208@zytor.com> References: <519DCBEF.3090208@asianux.com> <20130528081910.GA29557@gmail.com> <51A4C564.4040301@zytor.com> <201305281743.52649.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <201305281743.52649.arnd-r2nGTMty4D4@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: uclinux-dist-devel-bounces-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org Errors-To: uclinux-dist-devel-bounces-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org To: Arnd Bergmann Cc: Linux-sh list , Catalin Marinas , Benjamin Herrenschmidt , Chen Gang , Heiko Carstens , "paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org" , Michel Lespinasse , Ingo Molnar , Hans-Christian Egtvedt , Linux-Arch , linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Russell King - ARM Linux , Yoshinori Sato , Richard Weinberger , Helge Deller , the arch/x86 maintainers , "James E.J. Bottomley" , "mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org" , Geert Uytterhoeven List-Id: linux-arch.vger.kernel.org On 05/28/2013 08:43 AM, Arnd Bergmann wrote: > > Right, that is what the patch I just posted does. > > On a related note, I found that WARN_ON() can no longer be compiled > out since there is already code that relies on the side-effects of > the condition. I assume that was an intentional change I missed, > since it used to be defined so that you could remove it completely. > It is possible to define WARN_ON() as: #define WARN_ON(x) ((void)(x)) ... which preserves side effects. -hpa From mboxrd@z Thu Jan 1 00:00:00 1970 From: "H. Peter Anvin" Subject: Re: [PATCH] arch: configuration, deleting 'CONFIG_BUG' since always need it. Date: Tue, 28 May 2013 09:06:48 -0700 Message-ID: <51A4D618.3080208@zytor.com> References: <519DCBEF.3090208@asianux.com> <20130528081910.GA29557@gmail.com> <51A4C564.4040301@zytor.com> <201305281743.52649.arnd@arndb.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Cc: Linux-sh list , Catalin Marinas , Benjamin Herrenschmidt , Chen Gang , Heiko Carstens , "paulus-eUNUBHrolfbYtjvyW6yDsg@public.gmane.org" , Michel Lespinasse , Ingo Molnar , Hans-Christian Egtvedt , Linux-Arch , linux-s390-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, Russell King - ARM Linux , Yoshinori Sato , Richard Weinberger , Helge Deller , the arch/x86 maintainers , "James E.J. Bottomley" , "mingo-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org" , Geert Uytterhoeven , To: Arnd Bergmann Return-path: In-Reply-To: <201305281743.52649.arnd-r2nGTMty4D4@public.gmane.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: uclinux-dist-devel-bounces-ZG0+EudsQA8dtHy/vicBwGD2FQJk+8+b@public.gmane.org On 05/28/2013 08:43 AM, Arnd Bergmann wrote: > > Right, that is what the patch I just posted does. > > On a related note, I found that WARN_ON() can no longer be compiled > out since there is already code that relies on the side-effects of > the condition. I assume that was an intentional change I missed, > since it used to be defined so that you could remove it completely. > It is possible to define WARN_ON() as: #define WARN_ON(x) ((void)(x)) ... which preserves side effects. -hpa From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <51A4D618.3080208@zytor.com> Date: Tue, 28 May 2013 09:06:48 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 References: <519DCBEF.3090208@asianux.com> <20130528081910.GA29557@gmail.com> <51A4C564.4040301@zytor.com> <201305281743.52649.arnd@arndb.de> In-Reply-To: <201305281743.52649.arnd@arndb.de> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [PATCH] arch: configuration, deleting 'CONFIG_BUG' since always need it. To: Arnd Bergmann Cc: Ingo Molnar , Russell King - ARM Linux , Geert Uytterhoeven , Chen Gang , H?vard Skinnemoen , Hans-Christian Egtvedt , Mike Frysinger , Yoshinori Sato , Richard Kuo , "James E.J. Bottomley" , Helge Deller , Benjamin Herrenschmidt , "paulus@samba.org" , Martin Schwidefsky , Heiko Carstens , linux390@de.ibm.com, Paul Mundt , Jeff Dike , Richard Weinberger , Thomas Gleixner , "mingo@redhat.com" , the arch/x86 maintainers , "Eric W. Biederman" , Serge Hallyn , Paul McKenney , Frederic Weisbecker , David Miller , Andrew Morton , Akinobu Mita , Catalin Marinas , Michel Lespinasse , Will Deacon , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , "uclinux-dist-devel@blackfin.uclinux.org" , linux-hexagon@vger.kernel.org, Parisc List , "linuxppc-dev@lists.ozlabs.org" , linux-s390@vger.kernel.org, Linux-sh list , uml-devel , uml-user , Linux-Arch , Linus Torvalds List-ID: On 05/28/2013 08:43 AM, Arnd Bergmann wrote: > > Right, that is what the patch I just posted does. > > On a related note, I found that WARN_ON() can no longer be compiled > out since there is already code that relies on the side-effects of > the condition. I assume that was an intentional change I missed, > since it used to be defined so that you could remove it completely. > It is possible to define WARN_ON() as: #define WARN_ON(x) ((void)(x)) ... which preserves side effects. -hpa From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.zytor.com (terminus.zytor.com [IPv6:2001:1868:205::10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTPS id 1E7352C02BA for ; Wed, 29 May 2013 02:09:24 +1000 (EST) Message-ID: <51A4D618.3080208@zytor.com> Date: Tue, 28 May 2013 09:06:48 -0700 From: "H. Peter Anvin" MIME-Version: 1.0 To: Arnd Bergmann Subject: Re: [PATCH] arch: configuration, deleting 'CONFIG_BUG' since always need it. References: <519DCBEF.3090208@asianux.com> <20130528081910.GA29557@gmail.com> <51A4C564.4040301@zytor.com> <201305281743.52649.arnd@arndb.de> In-Reply-To: <201305281743.52649.arnd@arndb.de> Content-Type: text/plain; charset=ISO-8859-1 Cc: Catalin Marinas , Linux-sh list , Chen Gang , Heiko Carstens , "paulus@samba.org" , Michel Lespinasse , Ingo Molnar , Hans-Christian Egtvedt , Linux-Arch , linux-s390@vger.kernel.org, Russell King - ARM Linux , Yoshinori Sato , Richard Weinberger , Helge Deller , the arch/x86 maintainers , "James E.J. Bottomley" , "mingo@redhat.com" , Geert Uytterhoeven , Frederic Weisbecker , Paul McKenney , H?vard Skinnemoen , Serge Hallyn , Mike Frysinger , uml-devel , Will Deacon , Jeff Dike , Akinobu Mita , uml-user , "uclinux-dist-devel@blackfin.uclinux.org" , Thomas Gleixner , "linux-arm-kernel@lists.infradead.org" , Parisc List , Linus Torvalds , "linux-kernel@vger.kernel.org" , Richard Kuo , Paul Mundt , "Eric W. Biederman" , linux-hexagon@vger.kernel.org, Martin Schwidefsky , linux390@de.ibm.com, Andrew Morton , "linuxppc-dev@lists.ozlabs.org" , David Miller List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On 05/28/2013 08:43 AM, Arnd Bergmann wrote: > > Right, that is what the patch I just posted does. > > On a related note, I found that WARN_ON() can no longer be compiled > out since there is already code that relies on the side-effects of > the condition. I assume that was an intentional change I missed, > since it used to be defined so that you could remove it completely. > It is possible to define WARN_ON() as: #define WARN_ON(x) ((void)(x)) ... which preserves side effects. -hpa From mboxrd@z Thu Jan 1 00:00:00 1970 From: hpa@zytor.com (H. Peter Anvin) Date: Tue, 28 May 2013 09:06:48 -0700 Subject: [PATCH] arch: configuration, deleting 'CONFIG_BUG' since always need it. In-Reply-To: <201305281743.52649.arnd@arndb.de> References: <519DCBEF.3090208@asianux.com> <20130528081910.GA29557@gmail.com> <51A4C564.4040301@zytor.com> <201305281743.52649.arnd@arndb.de> Message-ID: <51A4D618.3080208@zytor.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On 05/28/2013 08:43 AM, Arnd Bergmann wrote: > > Right, that is what the patch I just posted does. > > On a related note, I found that WARN_ON() can no longer be compiled > out since there is already code that relies on the side-effects of > the condition. I assume that was an intentional change I missed, > since it used to be defined so that you could remove it completely. > It is possible to define WARN_ON() as: #define WARN_ON(x) ((void)(x)) ... which preserves side effects. -hpa