public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Darius Rad <darius@bluespec.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] include/linux/atomic.h: include asm-generic/atomic-long.h after asm-generic/atomic64.h
Date: Mon, 25 Aug 2014 11:33:03 -0400	[thread overview]
Message-ID: <53FB572F.1030803@bluespec.com> (raw)

Move the include of asm-generic/atomic-long.h to after the conditional
include of asm-generic/atomic64.h.  This is necessary if
CONFIG_GENERIC_ATOMIC64 is y and BITS_PER_LONG == 64, because
atomic-long.h uses functions declared in atomic64.h.

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/atomic.h |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

--- linux-3.17-rc1.orig/include/linux/atomic.h	2014-08-16 12:40:26.000000000 -0400
+++ linux-3.17-rc1/include/linux/atomic.h	2014-08-22 16:07:55.297515936 -0400
@@ -160,8 +160,8 @@ static inline void atomic_or(int i, atom
 }
 #endif /* #ifndef CONFIG_ARCH_HAS_ATOMIC_OR */
 
-#include <asm-generic/atomic-long.h>
 #ifdef CONFIG_GENERIC_ATOMIC64
 #include <asm-generic/atomic64.h>
 #endif
+#include <asm-generic/atomic-long.h>
 #endif /* _LINUX_ATOMIC_H */

                 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=53FB572F.1030803@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox