Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933004AbXEGLTv (ORCPT ); Mon, 7 May 2007 07:19:51 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S933012AbXEGLTv (ORCPT ); Mon, 7 May 2007 07:19:51 -0400 Received: from za-gw.sanpeople.com ([196.211.225.226]:2944 "EHLO za-gw.sanpeople.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933004AbXEGLTv (ORCPT ); Mon, 7 May 2007 07:19:51 -0400 X-Greylist: delayed 1325 seconds by postgrey-1.27 at vger.kernel.org; Mon, 07 May 2007 07:19:49 EDT Subject: Re: [PATCH 1/2] Use common cpu_is_xxx() macros on AT91 and AVR32 From: Andrew Victor To: Haavard Skinnemoen Cc: akpm@linux-foundation.org, David Brownell , Nicolas Ferre , linux-kernel@vger.kernel.org In-Reply-To: <11785276841920-git-send-email-hskinnemoen@atmel.com> References: <11785276841920-git-send-email-hskinnemoen@atmel.com> Content-Type: text/plain Organization: Multenet Technologies (Pty) Ltd Message-Id: <1178534593.27286.28.camel@fuzzie.sanpeople.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 Date: 07 May 2007 12:43:13 +0200 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 867 Lines: 21 > Several drivers shared between AT91 and AVR32 chips use cpu_is_xxx() > to handle CPU-specific differences. Currently, such code needs to be > inside #ifdef CONFIG_ARCH_AT91 because the macros don't exist on AVR32. > > By defining the same macros on both AT91 and AVR32, these #ifdefs can > be eliminated. Since the macros will evaluate to a constant value for > CPUs that aren't supported by the current architecture, any code that > is only needed on AT91 will be optimized away on AVR32 and vice versa. > > Signed-off-by: Haavard Skinnemoen Acked-by: Andrew Victor - 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/