linux-kernel - Re: [PATCH -mm -v5] Separate atomic_t declaration from asm/atomic.h into asm/atomic

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20081015153124.c560e97e.akpm@linux-foundation.org>
Date:	Wed, 15 Oct 2008 15:31:24 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Matthew Wilcox <matthew@....cx>
Cc:	mingo@...e.hu, ying.huang@...el.com, linux-kernel@...r.kernel.org,
	hpa@...or.com, tglx@...utronix.de
Subject: Re: [PATCH -mm -v5] Separate atomic_t declaration from asm/atomic.h
 into asm/atomic_def.h

On Wed, 15 Oct 2008 16:19:48 -0600
Matthew Wilcox <matthew@....cx> wrote:

> On Wed, Oct 15, 2008 at 03:11:19PM -0700, Andrew Morton wrote:
> > On Tue, 14 Oct 2008 12:47:19 -0600
> > Matthew Wilcox <matthew@....cx> wrote:
> > > 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.
> 
> Um, no.  Roman and I are against the creation of a new file.  Just put
> the atomic_t definition in <linux/types.h>.

Well we've been glacially fartarsing around with this for sufficiently
long that any such alterations will be too late for 2.6.28.

I'll drop it all.  Again.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/