Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932471AbVLIWUr (ORCPT ); Fri, 9 Dec 2005 17:20:47 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932479AbVLIWUr (ORCPT ); Fri, 9 Dec 2005 17:20:47 -0500 Received: from ns2.suse.de ([195.135.220.15]:1167 "EHLO mx2.suse.de") by vger.kernel.org with ESMTP id S932476AbVLIWUq (ORCPT ); Fri, 9 Dec 2005 17:20:46 -0500 Date: Fri, 9 Dec 2005 23:20:45 +0100 From: Andi Kleen To: Adrian Bunk Cc: Christoph Lameter , linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-ia64@ver.kernel.org, ak@suse.de Subject: Re: [RFC] Introduce atomic_long_t Message-ID: <20051209222045.GL11190@wotan.suse.de> References: <20051209201127.GE23349@stusta.de> <20051209220226.GG23349@stusta.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20051209220226.GG23349@stusta.de> Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 646 Lines: 16 > I'd say the sequence is: > 1. create an linux/atomic.h the #include's asm/atomic.h > 2. convert all asm/atomic.h to use linux/atomic.h > 3. move common code to linux/atomic.h I don't think there is much common code actually. atomic_t details vary widly between architectures. Just defining a few macros to others is really not significant. I think Christoph's original patch was just fine. -Andi - 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/