1. 16 Jan, 2006 2 commits
    • Komal Shah's avatar
      No commit message · fb60ce82
      Komal Shah authored
      No commit message
      fb60ce82
    • Komal Shah's avatar
      [PATCH] ARM: OMAP: fix linking · e8024a44
      Komal Shah authored
      Patch fixes following error, which gets generated if you don't select
      IrDA driver for H4.
      
      arch/arm/mach-omap2/built-in.o(.text+0x1844): In function read_gpio_expa'
      arch/arm/mach-omap2/built-in.o(.text+0x186c): In function write_gpio_expa'
      arch/arm/mach-omap2/built-in.o(.text+0x18ac): In function read_gpio_expa'
      arch/arm/mach-omap2/built-in.o(.text+0x18e4): In function write_gpio_expa'
      make: *** [.tmp_vmlinux1] Error 1
      Signed-off-by: default avatarKomal Shah <komal_shah802003@yahoo.com>
      Signed-off-by: default avatarTony Lindgren <tony@atomide.com>
      e8024a44
  2. 15 Jan, 2006 2 commits
  3. 14 Jan, 2006 7 commits
  4. 12 Jan, 2006 4 commits
  5. 05 Jan, 2006 4 commits
  6. 04 Jan, 2006 4 commits
  7. 03 Jan, 2006 15 commits
  8. 02 Jan, 2006 2 commits
    • Dag-Erling Smrgrav's avatar
      [PATCH] Avoid namespace pollution in <asm/param.h> · abe842eb
      Dag-Erling Smrgrav authored
      In commit 3D59121003721a8fad11ee72e646fd9d3076b5679c, the x86 and x86-64
      <asm/param.h> was changed to include <linux/config.h> for the
      configurable timer frequency.
      
      However, asm/param.h is sometimes used in userland (it is included
      indirectly from <sys/param.h>), so your commit pollutes the userland
      namespace with tons of CONFIG_FOO macros.  This greatly confuses
      software packages (such as BusyBox) which use CONFIG_FOO macros
      themselves to control the inclusion of optional features.
      
      After a short exchange, Christoph approved this patch
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      abe842eb
    • Benjamin Herrenschmidt's avatar
      [PATCH] powerpc: more g5 overtemp problem fix · f12f4d90
      Benjamin Herrenschmidt authored
      Some G5s still occasionally experience shutdowns due to overtemp
      conditions despite the recent fix. After analyzing logs from such
      machines, it appears that the overtemp code is a bit too quick at
      shutting the machine down when reaching the critical temperature (tmax +
      8) and doesn't leave the fan enough time to actually cool it down. This
      happens if the temperature of a CPU suddenly rises too high in a very
      short period of time, or occasionally on boot (that is the CPUs are
      already overtemp by the time the driver loads).
      
      This patches makes the code a bit more relaxed, leaving a few seconds to
      the fans to do their job before kicking the machine shutown.
      Signed-off-by: default avatarBenjamin Herrenschmidt <benh@kernel.crashing.org>
      Signed-off-by: default avatarLinus Torvalds <torvalds@osdl.org>
      f12f4d90