public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Dave Airlie <airlied@linux.ie>
Cc: linux-kernel@vger.kernel.org
Subject: Re: cmpxchg is not available to generic code
Date: Thu, 19 Jul 2007 01:10:55 -0700	[thread overview]
Message-ID: <20070719011055.1392c7d2.akpm@linux-foundation.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0707190900320.19586@skynet.skynet.ie>

On Thu, 19 Jul 2007 09:02:03 +0100 (IST) Dave Airlie <airlied@linux.ie> wrote:

> 
> 
> > arm:
> >
> > drivers/char/drm/drm_lock.c: In function `drm_lock_take':
> > drivers/char/drm/drm_lock.c:221: error: implicit declaration of function `cmpxchg'
> >
> > You might be able to use atomic_cmpxchg, which _is_ present
> > on all architectures.  Or use a spinlock.
> >
> > What's that code doing anyway?  driver-private locking primitives?
> 
> When did arm suddenly start wanting DRM?

It's selectable in config.  allmodconfig broke.

> they need to grow a userpsace 
> cmpxchg as davem mentioned to go along with this, changing the drm now 
> isn't possible due to backwards compat..

For reference purposes, that position is not acceptable.  We _never_ accept the
"oh I can't change my proposed kernel interface because I already have
userspace relying on it" argument.

Hopefully that won't be an issue here.  I guess DRM now needs a
`depends on !ARM'.


  reply	other threads:[~2007-07-19  8:25 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
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 [this message]
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=20070719011055.1392c7d2.akpm@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=airlied@linux.ie \
    --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