From: Matthew Wilcox <matthew@wil.cx>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ingo Molnar <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
Date: Tue, 14 Oct 2008 12:47:19 -0600 [thread overview]
Message-ID: <20081014184718.GG15064@parisc-linux.org> (raw)
In-Reply-To: <20081010155450.094288b4.akpm@linux-foundation.org>
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.
--
Matthew Wilcox Intel Open Source Technology Centre
"Bill, look, we understand that you're interested in selling us this
operating system, but compare it to ours. We can't possibly take such
a retrograde step."
next prev parent reply other threads:[~2008-10-14 18:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-08 9:44 [PATCH -mm -v5] Separate atomic_t declaration from asm/atomic.h into asm/atomic_def.h Huang Ying
2008-10-10 21:43 ` Andrew Morton
2008-10-10 21:49 ` Ingo Molnar
2008-10-10 22:54 ` Andrew Morton
2008-10-14 18:47 ` Matthew Wilcox [this message]
2008-10-15 22:11 ` Andrew Morton
2008-10-15 22:19 ` Matthew Wilcox
2008-10-15 22:31 ` Andrew Morton
2008-10-18 4:00 ` Matthew Wilcox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20081014184718.GG15064@parisc-linux.org \
--to=matthew@wil.cx \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox