From: Andrew Morton <akpm@linux-foundation.org>
To: Mike Frysinger <vapier@gentoo.org>
Cc: Luca Barbieri <luca@luca-barbieri.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] lib/atomic64_test: do not build on non-atomic64 systems
Date: Thu, 21 Oct 2010 15:02:50 -0700 [thread overview]
Message-ID: <20101021150250.f6499506.akpm@linux-foundation.org> (raw)
In-Reply-To: <1287250035-30404-1-git-send-email-vapier@gentoo.org>
On Sat, 16 Oct 2010 13:27:15 -0400
Mike Frysinger <vapier@gentoo.org> wrote:
> If the arch doesn't provide atomic64 functionality (there are quite a
> few), then don't bother trying to build this test.
>
I don't get it. If the arch doesn't implement atomic64 then this file
will get zillions of build errors, won't it?
> diff --git a/lib/atomic64_test.c b/lib/atomic64_test.c
> index 250ed11..0ac1a66 100644
> --- a/lib/atomic64_test.c
> +++ b/lib/atomic64_test.c
> @@ -12,6 +12,8 @@
> #include <linux/kernel.h>
> #include <asm/atomic.h>
>
> +#ifdef ATOMIC64_INIT
hm, that's a bit lazy. It should really use a CONFIG_HAVE_ thing. What
a pita.
> #define INIT(c) do { atomic64_set(&v, c); r = c; } while (0)
> static __init int test_atomic64(void)
> {
> @@ -164,3 +166,5 @@ static __init int test_atomic64(void)
> }
>
> core_initcall(test_atomic64);
> +
> +#endif
> --
> 1.7.3.1
next prev parent reply other threads:[~2010-10-21 22:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-16 17:27 [PATCH] lib/atomic64_test: do not build on non-atomic64 systems Mike Frysinger
2010-10-21 22:02 ` Andrew Morton [this message]
2010-10-21 22:23 ` Mike Frysinger
2010-10-21 22:55 ` Andrew Morton
2010-10-21 23:04 ` Mike Frysinger
2010-10-21 23:24 ` Andrew Morton
2010-10-22 20:14 ` Mike Frysinger
2010-10-22 20:31 ` Andrew Morton
2010-10-22 20:47 ` Mike Frysinger
2010-10-22 21:00 ` Andrew Morton
2010-10-22 21:07 ` Mike Frysinger
2010-10-24 16:20 ` Roland Dreier
2010-10-25 1:52 ` 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=20101021150250.f6499506.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luca@luca-barbieri.com \
--cc=vapier@gentoo.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.