linux-toradex.git/arch/mn10300, branch v2.6.38.8

MN10300: atomic_read() should ensure it emits a load

2011-03-14T14:51:25+00:00

atomic_read() needs to ensure that it emits a load (which it can do by using
ACCESS_ONCE()).

Reported-by: Peter Zijlstra 
Signed-off-by: David Howells

MN10300: The SMP_ICACHE_INV_FLUSH_RANGE IPI command does not exist

2011-03-14T14:45:29+00:00

The invalidate-only versions of flush_icache_*range() are trying sending the
SMP_ICACHE_INV_FLUSH_RANGE IPI command in SMP kernels when they should be
sending SMP_ICACHE_INV_RANGE as the former does not exist.

Signed-off-by: David Howells

MN10300: Proper use of macros get_user() in the case of incremented pointers

2011-03-14T14:44:30+00:00

Using __get_user_check(x, ptr++, size) leads to double increment of pointer.
This macro uses the macro get_user directly, which itself is used in this way
(get_user(x, ptr++)) in some functions of the kernel. The patch fixes the
error.

Reported-by: Tkhai Kirill 
Signed-off-by: David Howells

mn10300: Use generic irq Kconfig

2011-01-21T10:55:33+00:00

No functional change.

Signed-off-by: Thomas Gleixner 
Acked-by: David Howells

genirq: Remove __do_IRQ

2011-01-21T10:55:31+00:00

All architectures are finally converted. Remove the cruft.

Signed-off-by: Thomas Gleixner 
Cc: Richard Henderson 
Cc: Mike Frysinger 
Cc: David Howells 
Cc: Tony Luck 
Cc: Greg Ungerer 
Cc: Michal Simek 
Acked-by: David Howells 
Cc: Kyle McMartin 
Acked-by: Benjamin Herrenschmidt 
Cc: Chen Liqin 
Cc: "David S. Miller" 
Cc: Chris Metcalf 
Cc: Jeff Dike

kconfig: rename CONFIG_EMBEDDED to CONFIG_EXPERT

2011-01-21T01:02:05+00:00

The meaning of CONFIG_EMBEDDED has long since been obsoleted; the option
is used to configure any non-standard kernel with a much larger scope than
only small devices.

This patch renames the option to CONFIG_EXPERT in init/Kconfig and fixes
references to the option throughout the kernel.  A new CONFIG_EMBEDDED
option is added that automatically selects CONFIG_EXPERT when enabled and
can be used in the future to isolate options that should only be
considered for embedded systems (RISC architectures, SLOB, etc).

Calling the option "EXPERT" more accurately represents its intention: only
expert users who understand the impact of the configuration changes they
are making should enable it.

Reviewed-by: Ingo Molnar 
Acked-by: David Woodhouse 
Signed-off-by: David Rientjes 
Cc: Greg KH 
Cc: "David S. Miller" 
Cc: Jens Axboe 
Cc: Arnd Bergmann 
Cc: Robin Holt 
Cc: 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

kernel: clean up USE_GENERIC_SMP_HELPERS

2011-01-13T16:03:08+00:00

For arch which needs USE_GENERIC_SMP_HELPERS, it has to select
USE_GENERIC_SMP_HELPERS, rather than leaving a choice to user, since they
don't provide their own implementions.

Also, move on_each_cpu() to kernel/smp.c, it is strange to put it in
kernel/softirq.c.

For arch which doesn't use USE_GENERIC_SMP_HELPERS, e.g.  blackfin, only
on_each_cpu() is compiled.

Signed-off-by: Amerigo Wang 
Cc: David Howells 
Cc: Thomas Gleixner 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: Yinghai Lu 
Cc: Peter Zijlstra 
Cc: Randy Dunlap 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

set_rtc_mmss: show warning message only once

2011-01-13T16:03:07+00:00

Occasionally the system gets into a state where the CMOS clock has gotten
slightly ahead of current time and the periodic update of RTC fails.  The
message is a nuisance and repeats spamming the log.

  See: http://www.ntp.org/ntpfaq/NTP-s-trbl-spec.htm#Q-LINUX-SET-RTC-MMSS

Rather than just removing the message, make it show only once and reduce
severity since it indicates a normal and non urgent condition.

Signed-off-by: Stephen Hemminger 
Cc: Richard Henderson 
Cc: Ivan Kokshaysky 
Cc: Matt Turner 
Cc: Ralf Baechle 
Cc: David Howells 
Cc: Paul Mundt 
Cc: Ingo Molnar 
Cc: "H. Peter Anvin" 
Cc: Thomas Gleixner 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

arch/mn10300/kernel/irq.c: fix build

2011-01-04T00:36:33+00:00

Addresses https://bugzilla.kernel.org/show_bug.cgi?id=25702

Reported-by: Martin Ettl 
Cc: David Howells 
Signed-off-by: Andrew Morton 
Signed-off-by: Linus Torvalds

clarify a usage constraint for cnt32_to_63()

2010-12-20T17:07:35+00:00

The cnt32_to_63 algorithm relies on proper counter data evaluation
ordering to work properly. This was missing from the provided
documentation.

Let's augment the documentation with the missing usage constraint and
fix the only instance that got it wrong.

Signed-off-by: Nicolas Pitre 
Acked-by: David Howells 
Signed-off-by: Linus Torvalds