linux-toradex.git, branch v2.6.28.8

Linux 2.6.28.8

2009-03-17T00:50:03+00:00

hwmon: (it87) Properly decode -128 degrees C temperature

2009-03-17T00:32:46+00:00

commit e267d25005c861fe6afda343f044536342c9f8b4 upstream

The it87 driver is reporting -128 degrees C as +128 degrees C.
That's not a terribly likely temperature value but let's still
get it right, especially when it simplifies the code.

Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman

MIPS: compat: Implement is_compat_task.

2009-03-17T00:32:46+00:00

commit 4302e5d53b9166d45317e3ddf0a7a9dab3efd43b upstream.

This is a build fix required after "x86-64: seccomp: fix 32/64 syscall
hole" (commit 5b1017404aea6d2e552e991b3fd814d839e9cd67).  MIPS doesn't
have the issue that was fixed for x86-64 by that patch.

This also doesn't solve the N32 issue which is that N32 seccomp processes
will be treated as non-compat processes thus only have access to N64
syscalls.

Signed-off-by: Ralf Baechle 
Signed-off-by: Linus Torvalds 
Signed-off-by: Greg Kroah-Hartman

drm/i915: Add missing userland definitions for gem init/execbuffer.

2009-03-17T00:32:46+00:00

commit 8d391aa410ecb230fc4c3147b94eec25b9f3c20f upstream.

fdo bug #19132.

Signed-off-by: Eric Anholt 
Signed-off-by: Dave Airlie 
Signed-off-by: Greg Kroah-Hartman

hwmon: (f71882fg) Hide misleading error message

2009-03-17T00:32:46+00:00

commit 603eaa1bdd3e0402085e815cc531bb0a32827a9e upstream

If the F71882FG chip is at address 0x4e, then the probe at 0x2e will
fail with the following message in the logs:
f71882fg: Not a Fintek device

This is misleading because there is a Fintek device, just at a
different address. So I propose to degrade this message to a debug
message.

Signed-off-by: Jean Delvare 
Acked-by: Hans de Goede

crypto: api - Fix algorithm test race that broke aead initialisation

2009-03-17T00:32:45+00:00

commit b8e15992b420d09dae831125a623c474c8637cee upstream.

When we complete a test we'll notify everyone waiting on it, drop
the mutex, and then remove the test larval (after reacquiring the
mutex).  If one of the notified parties tries to register another
algorithm with the same driver name prior to the removal of the
test larval, they will fail with EEXIST as only one algorithm of
a given name can be tested at any time.

This broke the initialisation of aead and givcipher algorithms as
they will register two algorithms with the same driver name, in
sequence.

This patch fixes the problem by marking the larval as dead before
we drop the mutex, and also ignoring all dead or dying algorithms
on the registration path.

Tested-by: Andreas Steffen 
Signed-off-by: Herbert Xu 
Cc: Kerin Millar 
Signed-off-by: Greg Kroah-Hartman

ACPI: fix broken usage of acpi_ut_get_node_name()

2009-03-17T00:32:45+00:00

This issue was fixed indirectly in mainline by commit
60a4ce7f4148155d3f28eea4a213f7ee47cd57b7.

acpi_ut_get_node_name() returns a four char fixed-size array, not
NULL-terminated.

This is the minimal fix for stable 2.6.28.

Signed-off-by: Henrique de Moraes Holschuh 
Cc: stable@kernel.org
Acked-by: Lin Ming 
Acked-by: Len Brown 
Signed-off-by: Greg Kroah-Hartman

ACPI: fix broken usage of name.ascii

2009-03-17T00:32:45+00:00

This issue was fixed indirectly in mainline by commit
0175d562a29ad052c510782c7e76bc63d5155b9b.

acpi_namespace_node's name.ascii field is four chars, and not NULL-
terminated except by pure luck.  So, it cannot be used by sscanf() without
a length restriction.

This is the minimal fix for both stable 2.6.27 and 2.6.28.

Signed-off-by: Henrique de Moraes Holschuh 
Cc: Lin Ming 
Cc: Len Brown 
Signed-off-by: Greg Kroah-Hartman

i2c: Fix misplaced parentheses

2009-03-17T00:32:45+00:00

commit f29d2e0275a4f03ef2fd158e484508dcb0c64efb upstream

Fix misplaced parentheses.

Signed-off-by: Roel Kluin 
Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman

i2c: Timeouts reach -1

2009-03-17T00:32:45+00:00

commit a746b578d8406b2db0e9f0d040061bc1f78433cf upstream

With a postfix decrement these timeouts reach -1 rather than 0, but
after the loop it is tested whether they have become 0.

As pointed out by Jean Delvare, the condition we are waiting for should
also be tested before the timeout. With the current order, you could
exit with a timeout error while the job is actually done.

Signed-off-by: Roel Kluin 
Signed-off-by: Jean Delvare 
Signed-off-by: Greg Kroah-Hartman