From: Andrew Morton <akpm@linux-foundation.org>
To: "Dave Airlie" <airlied@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
airlied@linux.ie, linux-kernel@vger.kernel.org
Subject: Re: cmpxchg is not available to generic code
Date: Thu, 19 Jul 2007 01:21:41 -0700 [thread overview]
Message-ID: <20070719012141.47911bd7.akpm@linux-foundation.org> (raw)
In-Reply-To: <21d7e9970707190115r15e691d5s123c9889a8ebd8a5@mail.gmail.com>
On Thu, 19 Jul 2007 18:15:03 +1000 "Dave Airlie" <airlied@gmail.com> wrote:
> Maybe we could add CONFIG_HAVE_CMPXCHG and let DRM depend on it..
That would certainly be better than adding a sprinkle of architectures
in DRM Kconfig dependencies.
I don't know how important DRM is on ARM. Zero?
next prev parent reply other threads:[~2007-07-19 8:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-19 7:05 cmpxchg is not available to generic code Andrew Morton
2007-07-19 7:27 ` David Miller
2007-07-19 8:15 ` Dave Airlie
2007-07-19 8:21 ` Andrew Morton [this message]
2007-07-19 8:23 ` Dave Airlie
2007-07-23 6:48 ` Nick Piggin
2007-07-19 20:54 ` David Miller
2007-07-19 20:58 ` David Miller
2007-07-19 8:02 ` Dave Airlie
2007-07-19 8:10 ` Andrew Morton
2007-07-19 8:19 ` Dave Airlie
2007-07-19 8:36 ` Andrew Morton
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=20070719012141.47911bd7.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=airlied@gmail.com \
--cc=airlied@linux.ie \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
/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