From: Stephen Smalley <sds@epoch.ncsc.mil>

Looking at d_splice_alias, it appears that the security_d_instantiate call
in the first case (where it ends up moving an entry in place of the given
dentry) should be passing 'new' rather than 'dentry' to ensure that the
passed dentry is associated with the inode.  This patch should fix the
problem.

(Addresses bugzilla #2153)

ext3_error() sleeps, so don't call it with the lock held.

From: Andi Kleen <ak@suse.de>,
      From Suresh.B.Siddha

Fix another bug caused by the recent IA32e merge.  The full L1 cache size
padding of the GDT didn't work with smaller cache line sizes.  Just revert
that.

I must admit I still don't understand why it didn't work, but it's better
to have a working system for now.

From: Xose Vazquez Perez <xose@wanadoo.es>

Even master's books bring errors :-).  URL has the errata and more
information about the books

From: "Randy.Dunlap" <rddunlap@osdl.org>

This patch tries to clean up init section usage in
arch/i386/kernel/cpu/mtrr/*.c.

From: Geert Uytterhoeven <geert@linux-m68k.org>

When compiling the IPMI drivers on m68k, I needed a few more includes:

  - <asm/irq.h> (for disable_irq_nosync() and enable_irq())

  - <linux/types.h> (for size_t)

  - <asm/system.h> (for printk())

From: Manfred Spraul <manfred@colorfullife.com>

Attached is a patch that replaces the #ifndef CONFIG_SYSV syscall stubs
with cond_syscall stubs.

From: Paul Clements <Paul.Clements@SteelEye.com>

This patch removes the PARANOIA define (it was always defined anyway).  It
also removes the requests_in/out counters (which weren't always accurate,
and are superfluous anyway, since the block layer keeps its own in_flight
counter).  Also some minor cleanup of comments.

From: Paul Clements <Paul.Clements@SteelEye.com>

This patch fixes the initial set_capacity call so that it matches nbd's
internal device size (nbd_device->bytesize).

From: bert hubert <ahu@ds9a.nl>

Current bitkeeper features a cryptoloop which is not safe for journaled
file systems and also a Device Mapper target which is.  The patch below
updates Kconfig to that effect.

If you pass a huge nlen value into sys_sysctl() it will loop for hours
printing billions of question marks, so range-check the arguments.

Also, remove the code which informs the user that the sysctl is obsolete: it
allows unprivileged users to spam the logs.

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k core spelling fix (from Michael Hayes)

From: Geert Uytterhoeven <geert@linux-m68k.org>

Add a dummy <asm-generic/dma-mapping-broken.h> for systems that don't support
the new DMA API, and make m68k use it if !CONFIG_PCI

From: Geert Uytterhoeven <geert@linux-m68k.org>

Mac IOP spelling fix (from Matthias Urlichs)

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k FPU emu: Remove reference to non-existing website

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k: Add missing implementation of cmpxchg() (from Andreas Schwab, Roman
Zippel and me)

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k: Improve formatting of call trace output (from Matthias Urlichs)

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k: Add missing relocation support to module loader (from Matthias Urlichs)

From: Geert Uytterhoeven <geert@linux-m68k.org>

Clean up arch/m68k/mm/Makefile logic

From: Geert Uytterhoeven <geert@linux-m68k.org>

Update M68k configuration logic:
  - Introduce CONFIG_MMU_MOTOROLA and CONFIG_MMU_SUN3
  - Move Sun-3 config selection to the top since all other platforms conflict
    with it
  - Sun-3 implies MMU_SUN3
  - All other platforms imply MMU_MOTOROLA
  - Sun-3 implies M68020
  - Sun-3x implies M68030
  - Sun-3 kernels cannot support 68030, 68040, or 68060

From: Geert Uytterhoeven <geert@linux-m68k.org>

Amifb: Fix bugs in the video mode database:
  - ntsc-lace lacks the yres value
  - a2024-15 is 15 Hz, not 10

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k: Use drivers/Kconfig and fix up some remaining dependencies:
  - M68k no longer uses rtc.c
  - M68k never has AGP
  - CONFIG_ZORRO depends on CONFIG_AMIGS

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k: Remove obsolete MCA definition

From: Geert Uytterhoeven <geert@linux-m68k.org>

Atari Falcon: Prepend falcon_ to some Atari Falcon definitions to solve name
clashes in some drivers.

From: Geert Uytterhoeven <geert@linux-m68k.org>

Sun-3 sbus: Add missing definition of sbus_readl() (from Sam Creasey)

From: Geert Uytterhoeven <geert@linux-m68k.org>

Sun-3: Use dummycon if CONFIG_DUMMY_CONSOLE is defined only (from Sam
Creasey)

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k mm: Kill warning (from Sam Creasey)

From: Geert Uytterhoeven <geert@linux-m68k.org>

M68k offsets.h: Move arch/m68k/kernel/m68k_defs.h to include/asm/offsets.h
and use gen-asm-offsets framework (from Andreas Schwab and Ray Knight)

From: Paul Clements <Paul.Clements@SteelEye.com>

Fix a module unload oops, as well as fix some return codes (so nbd-client
can exit with the proper error code, rather than 0, when an error occurs).

From: "H. Peter Anvin" <hpa@transmeta.com>

Remove the limit of 2048 pty's - allocate them on demand up to the 12:20
dev_t limit: a million.

From: Nick Piggin <piggin@cyberone.com.au>

sys_shmat() need to be declared asmlinkage.  This causes breakage when we
actually get the proper prototypes into caller's scope.

From: Terence Ripperda <tripperda@nvidia.com>

When coming out of standby, some chipsets lose their configuration in pci
config space.  this includes not just the agp master register being lost, but
chipset-specific information, such as the physical address of the gatt table
and other settings.  Calling this configure routine again restores those
settings.

Dave said he was adding chipsets to this list on an "as needed and tested"
basis.  I ran across this problem I believe on a Dell Inspiron 4100 with
nv11.  (there had been some similar problems with specific nv11 systems when
doing apm with the 2.4 kernel, I suspect, but haven't been able to verify,
it's the same problem).

From: Russell King <rmk@arm.linux.org.uk>

Here is a patch which updates various serial drivers in the kernel to make
them less broken than they were before.  Nevertheless, they are still
broken.

The improvement is to make these drivers use the tiocmget/tiocmset methods,
which are present in the 2.6 kernel.

Many of these have been incorrectly converted from the old global IRQ
locking without regard for SMP issues, or still use the old global IRQ
locking methods which are no longer present in 2.6 kernels.

The full message thread can be found at:

http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=1dvnl-5Pr-1%40gated-at.bofh.it&rnum=1&prev=/groups%3Fhl%3Den%26lr%3D%26ie%3DISO-8859-1%26q%3DOutstanding%2Bfixups%26btnG%3DGoogle%2BSearch%26meta%3Dgroup%253Dlinux.kernel

From: Russell King <rmk@arm.linux.org.uk>

Convert a bunch of serial drivers to new-style ioctl handling.

into ppc970.osdl.org:/home/torvalds/v2.5/linux

A bit too over-eager to minimise the delta resulted in this Kconfig
file trying to source a currently non-existent Kconfig file.

ARM720T processors use the "late" abort option, which means we have to
correct the base address of any page fault ourselves.  However, we
were mis-correcting the thumb "push" instruction, causing the retried
instruction to fail in a spectacular way.

Patch from: Peter Teichmann, edited by Russell King.

* a bugfix to the pseudo palette handling in 16/32 bit modes: the
  pseudo palette is always kept in 32 bit integers
* a bugfix to setcolreg() in 16 bit modes: there have to be 32 colour
  registers (this has nothing to do with the 16 pseudo palette
  colours, it is a bit misleading that setcolreg() is used both for
  pseudo palette setup and DIRECTCOLOR colour translation)
  (The behaviour should be selected using the visual and the rgb
   representation rather than the current BPP setting. --rmk)
* change 16 bit visual from TRUECOLOR to DIRECTCOLOR
* take the limited bandwidth of the RiscPC video memory into account
  for acornfb_valid_pixrate()
* acornfb_vidc20_find_rates() now takes into account the differences
  between VRAM and DRAM when setting the FIFO preload value. With
  VRAM, the FIFO can be set to the highest possible setting because
  there are no latency considerations for other memory accesses.
  However, in 64 bit bus mode the FIFO preload value must not be set
  to VIDC20_CTRL_FIFO_28 because this will let the FIFO overflow.
  See VIDC20 manual page 33 (6.0 Setting the FIFO preload value).

* select Multifreq monitor as default, increase frequency range for
  Multifreq monitor (this is of course a philosophical question, but
  I believe a sensible default setting should not impose too much
  limits to the user)
  (I dropped this change because it is known that some monitor
   hardware shipped with Acorn machines does not take kindly to
   wrong timing signals.  If people really care, they should use
   the kernel command line to select the correct monitor type. --rmk) 

Use the SA1111 GPIO functionality added by the previous cset to
ensure that GPIOs are modified atomically.