Date: Wed, 15 Oct 2008 15:11:19 -0700
From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <matthew@wil.cx>
Cc: mingo@elte.hu, ying.huang@intel.com, linux-kernel@vger.kernel.org,
       hpa@zytor.com, tglx@linutronix.de
Subject: Re: [PATCH -mm -v5] Separate atomic_t declaration from asm/atomic.h
 into asm/atomic_def.h
Message-Id: <20081015151119.493ea13f.akpm@linux-foundation.org>
In-Reply-To: <20081014184718.GG15064@parisc-linux.org>
References: <1223459070.5872.167.camel@yhuang-dev.sh.intel.com>
	<20081010144335.65d8153b.akpm@linux-foundation.org>
	<20081010214958.GA7708@elte.hu>
	<20081010155450.094288b4.akpm@linux-foundation.org>
	<20081014184718.GG15064@parisc-linux.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1244
Lines: 33

On Tue, 14 Oct 2008 12:47:19 -0600
Matthew Wilcox <matthew@wil.cx> wrote:

> On Fri, Oct 10, 2008 at 03:54:50PM -0700, Andrew Morton wrote:
> > I have a note here that Matthew has proposed a different way of doing
> > all this.  I don't immediately recall the details.
> > 
> > Can we get a refresh on all of that please?
> 
> I didn't remember either, but having just reviewed my inbox from August,
> I said that all architectures basically use:
> 
> typedef struct { volatile int counter; } atomic_t;
> #ifdef CONFIG_64BIT
> typedef struct { volatile long counter; } atomic64_t;
> #endif
> 
> and that should just be put in <linux/atomic_types.h>.
> 
> Roman Zippel did me one better and suggested just putting it in types.h,
> which works for me.

OK.  Or we could do the usual include/asm-generic/atomic_types.h and
then architectures can choose to include that if it is appropriate.

Anyway the good news is that this concept is an addition to rather than
a replacement of this current patch.

--
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/