All of lore.kernel.org
 help / color / mirror / Atom feed
From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Greg Ungerer <gerg@snapgear.com>
Cc: linux-m68k@vger.kernel.org, gerg@uclinux.org
Subject: Re: [PATCH v2] m68k/m68knommu: merge MMU and non-MMU atomic.h
Date: Wed, 8 Sep 2010 21:45:37 +0200	[thread overview]
Message-ID: <AANLkTi=_cyyD8ub0vzqf9fbBFt4RoNPvJJCHUtVSgFqQ@mail.gmail.com> (raw)
In-Reply-To: <201009080031.o880VBpV031375@goober.internal.moreton.com.au>

On Wed, Sep 8, 2010 at 02:31, Greg Ungerer <gerg@snapgear.com> wrote:
> From 31b4a9fff37587b571f24b005cee47e3ac8485ac Mon Sep 17 00:00:00 2001
> From: Greg Ungerer <gerg@uclinux.org>
> Date: Mon, 6 Sep 2010 12:49:41 +1000
> Subject: [PATCH 6/8] m68k/m68knommu: merge MMU and non-MMU atomic.h
>
> The only difference between the MMU and non-MMU versions of atomic.h
> is some extra support needed by ColdFire family processors. So merge
> this into the MMU version of atomic.h.

[...]

> @@ -197,4 +207,5 @@ static __inline__ int atomic_add_unless(atomic_t *v, int a, int u)
>  #define smp_mb__after_atomic_inc()     barrier()
>
>  #include <asm-generic/atomic-long.h>
> +#include <asm-generic/atomic64.h>
>  #endif /* __ARCH_M68K_ATOMIC __ */

Thanks, the new one builds fine.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds

      reply	other threads:[~2010-09-08 19:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-08  0:31 [PATCH v2] m68k/m68knommu: merge MMU and non-MMU atomic.h Greg Ungerer
2010-09-08 19:45 ` Geert Uytterhoeven [this message]

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='AANLkTi=_cyyD8ub0vzqf9fbBFt4RoNPvJJCHUtVSgFqQ@mail.gmail.com' \
    --to=geert@linux-m68k.org \
    --cc=gerg@snapgear.com \
    --cc=gerg@uclinux.org \
    --cc=linux-m68k@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.