From: Darius Rad <darius@bluespec.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] include/linux/types.h: avoid duplicate definition of atomic64_t when 64BIT && GENERIC_ATOMIC64
Date: Mon, 25 Aug 2014 11:32:59 -0400 [thread overview]
Message-ID: <53FB572B.20401@bluespec.com> (raw)
If CONFIG_64BIT and CONFIG_GENERIC_ATOMIC64 are both y, atomic64_t is
defined in both include/linux/types.h and include/asm-generic/atomic64.h.
Allow the definition in include/asm-generic/atomic64.h to prevail, since
that definition is consistent with the rest of CONFIG_GENERIC_ATOMIC64.
Signed-off-by: Darius Rad <darius@bluespec.com>
---
It does not appear that this is relevant to architectures that are in the
kernel tree (i.e., no architectures use GENERIC_ATOMIC64 on 64-bit). It
is relevant, however, to certain combinations of options for the RISC-V
architecture currently in development.
Patch generated against 3.17-rc1.
include/linux/types.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- linux-3.17-rc1.orig/include/linux/types.h 2014-08-16 12:40:26.000000000 -0400
+++ linux-3.17-rc1/include/linux/types.h 2014-08-22 14:27:03.012782185 -0400
@@ -177,7 +177,7 @@ typedef struct {
int counter;
} atomic_t;
-#ifdef CONFIG_64BIT
+#if defined(CONFIG_64BIT) && !defined(CONFIG_GENERIC_ATOMIC64)
typedef struct {
long counter;
} atomic64_t;
reply other threads:[~2014-08-25 15:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53FB572B.20401@bluespec.com \
--to=darius@bluespec.com \
--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 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.