This patch moves common ColdFire vector and timer procesing code from
the local per-processor config.c for the 5407 ColdFire sub-architecture.
All ColdFire CPU's have the same timer and basic vector setup, seems
crazy to repeat this code for each of 6 ColdFire CPU varients.

This patch fixes up the PCI bios header for the m68knommu COMEM-lite
PCI hardware support. Adds missing definitions, and a couple of trivial
inline functions here.

This patches add an include to stddef.h into include/linux/list.h.
It uses the NULL define.

This patch is the last of the MMUless support changes to the mm system.
It inlines for MMUless targets the following functions:

	vmalloc_to_page()
	follow_page()
	remap_page_range()

All of these return NULL for the non-MMU case. Doing the inline here
minimizes changes to assorted mm/ files. This patch was originally
from Christoph Hellwig.

This patch fixes a wrong m68knommu/68360 config define,
CONFIG_68630_SCC -> CONFIG_68360_SCC.

This patch moves common ColdFire vector and timer procesing code from
the local per-processor config.c for the 5307 ColdFire sub-architecture.
All ColdFire CPU's have the same timer and basic vector setup, seems
crazy to repeat this code for each of 6 ColdFire CPU varients.
This patch also removes the reset button support, this is now moved to
a proper device driver, where it belongs.

This patch adds a call to schedule_tail() in the return from fork
post processing.

This patch fixes the m68knomu/68VZ328/ucdimm Makefile to build all its
local code files. Previously it relied on Makefiles above it to do
this. It should be done here.

This patch fixes the m68knomu/68VZ328/de2 Makefile to build all its
local code files. Previously it relied on Makefiles above it to do
this. It should be done here.

This patch moves common ColdFire vector and timer procesing code from
the local per-processor config.c for the 5272 ColdFire sub-architecture.
All ColdFire CPU's have the same timer and basic vector setup, seems
crazy to repeat this code for each of 6 ColdFire CPU varients.
This patch also removes the reset button support, this is now moved to
a proper device driver, where it belongs.

This patch fixes up a lot of problems in the m68knommu architecture
CO-MEMlite PCI interface code. The code was seriously out of date,
not implementing many of the requried PCI bios support functions.
Also fixes many wrong function return types and arguments.

Fix m68knommu 68VZ328 Makefile to only traverse its sub-directories.
There is no local code files for it to compile.

Include errno.h in the m68knommu 68360 specific interrupt setup code.
It needs a few E* types as return values.

Fix wrong argument prototype in m68knommu commproc.c.

This patch fixes the m68knommu de2 platform config to use the generic
68328 irq setup. All 68*328 family can use the same setup.

This patch fixes a couple of spelling errors in the m68knommy Kconfig
help entries. Also makes CONFIG_HIGHPROFILE dependant on CONFIG_COLDFIRE,
since that feature is only implemented on ColdFIre based platforms.

This patch fixes the m68knommu ucdimm platform config to use the generic
68328 irq setup. All 68*328 family can use the same setup.

Include errno.h in the m68knommu 68328 specific interrupt setup code.
It needs a few E* types as return values.

Include asm/unistd.h to get the NR_syscalls definition in the
m68knommu 68328 interrupt entry code.

Include asm/unistd.h to get the NR_syscalls definition in the
m68knommu 68360 interrupt entry code.

Here is the latest round of EISA/sysfs update.

 - Add documentation,
 - Add support for per EISA-id driver data,
 - Move virtual_root device to a platform device,
 - Update CREDITS.

Here is the parisc part of the patch with Willy's blessing.

Here is the s390x part of the patch with Martin's blessing.

Here is the x86_64 part of the patch with Andi's blessing.

This patch creates compat_sys_fcntl{,64}.  The diffstat for the whole
patch set is below, but this is just the generic part, the architecture
specific parts will follow.

This patch also removes struct flock64 from all the 64 bit architectures
(except parisc).

into tetrachloride.(none):/mnt/raid/src/kernel/2.5/cpufreq

Patch from Dave Miller.  Fixes a very long-standing bug.

If a process has an fd open against a now-removed directory, lookups on that
fd will end up calling ext2_find_entry() against a zero-length directory.

When this happens ext2_find_entry() will, on the first pass through the loop,
set `kaddr' to page_address(page) - 20.  Things get confused and the "zero
length directory entry" warning triggers.

This only happens on 64-bit machines, because ext2_last_byte() is returning
an unsigned (32-bit) value, and the arithmetic works out OK for 32-bit
machines.

So we change ext2_find_entry() to bale out immediately if the directory is
zero-length.  All other directory-walking functions do this, but
ext2_find_entry() forgot to, due to the search-from-the-last-place
optimisation.

Fix a couple of ext3 error handling routines to not assume that the
superblock has valid journal and buffer_head pointers.  These functions are
called during mount and unmount and that may not be true.

This should fix the oops which Zwane saw when mounting a corrupt filesystem.

I enabled the advanced use-after-free detector for large slab objects and the
kernel oopsed.  This is because that debug code adds things at the head of
the slab objects, and the kernel will die if task_structs are not
well-aligned.

The way to tell the slab allocator that it is not allowed to misalign objects
from this slab is SLAB_MUST_HWCACHE_ALIGN.

Patch from Oleg Drokin <green@linuxhacker.ru>

There seems to be a memleak on error exit path.

Patch from Oleg Drokin <green@linuxhacker.ru>

   Not freeing allocated memory on error exit path.

Patch from Petr Vandrovec <vandrove@vc.cvut.cz>
Reported by Oleg Drokin.

    In NCP_IOC_SETOBJECTNAME handler, we allocated space (newname pointer),
    copy stuff from userspace to there and then assign userspace
    pointer to our internal structure, whoops!

Force inlining even when gcc-3.x is too confused to do it for us.

The conversion of the console registration to an initcall-style thing has
broken lots of people's setups.  It is now dependent upon linkage order and
if you have both CONFIG_VT_CONSOLE and CONFIG_SERIAL_CONSOLE, no boot
messages come out on the screen because the kernel is selecting the serial
console first.

It can be fixed by specifying console=tty0, but nobody is doing that.

We can fix it up by placing drivers/char/ in front of drivers/serial/ in
linkage order.

The pnp_request_card_device() stub should return NULL, not -ENODEV.

Patch from Andreas Mohr <andi@rhlx01.fht-esslingen.de>

Need to retake the spinlock in __pdflush() before continuing.