The patch titled
Subject: m32r: allow use of atomic64
has been added to the -mm tree. Its filename is
m32r-allow-use-of-atomic64.patch
Before you just go and hit "reply", please:
a) Consider who else should be cc'ed
b) Prefer to cc a suitable mailing list as well
c) Ideally: find the original patch on the mailing list and do a
reply-to-all to that, adding suitable additional cc's
*** Remember to use Documentation/SubmitChecklist when testing your code ***
See http://userweb.kernel.org/~akpm/stuff/added-to-mm.txt to find
out what to do about this
The current -mm tree may be found at http://userweb.kernel.org/~akpm/mmotm/
------------------------------------------------------
From: Steven Rostedt <rostedt@xxxxxxxxxxx>
Subject: m32r: allow use of atomic64
Atomic64 is now a valid type in Linux. Archs that do not have their own
version of atomic64 operators are to use the generic operations.
The m32r architecture needs to define GENERIC_ATOMIC64.
Link: http://lkml.kernel.org/r/20111013085936.GA13046@xxxxxxx
Signed-off-by: Steven Rostedt <rostedt@xxxxxxxxxxx>
Reported-by: Ingo Molnar <mingo@xxxxxxx>
Cc: Hirokazu Takata <takata@xxxxxxxxxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxx>
---
arch/m32r/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff -puN arch/m32r/Kconfig~m32r-allow-use-of-atomic64 arch/m32r/Kconfig
--- a/arch/m32r/Kconfig~m32r-allow-use-of-atomic64
+++ a/arch/m32r/Kconfig
@@ -10,6 +10,7 @@ config M32R
select HAVE_GENERIC_HARDIRQS
select GENERIC_IRQ_PROBE
select GENERIC_IRQ_SHOW
+ select GENERIC_ATOMIC64
config SBUS
bool
_
Subject: Subject: m32r: allow use of atomic64
Patches currently in -mm which might be from rostedt@xxxxxxxxxxx are
origin.patch
linux-next.patch
m32r-allow-use-of-atomic64.patch
stop_machine-make-stop_machine-safe-and-efficient-to-call-early.patch
cgroup-kmemleak-annotate-alloc_page-for-cgroup-allocations.patch
memcg-fix-race-condition-in-memcg_check_events-with-this_cpu-usage.patch
--
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
