into touki.austin.ibm.com:/home/jgrimm/bk/lksctp-2.5.work

Splitting out yet more code.  New af and pf specific functions. 

into touki.austin.ibm.com:/home/jgrimm/bk/lksctp-2.5.work

Replace sockaddr_storage_t with 'union sctp_addr'.
Split up more ipv4/ipv6 code into af specific functions.
More later, but this gives me a base to do the rest.

into dyn9-47-18-140.beaverton.ibm.com:/home/sridhar/BK/lksctp-2.5.46

into dyn9-47-18-140.beaverton.ibm.com:/home/sridhar/BK/lksctp-2.5.46

Both the /proc/sys/cpu/ and /proc/cpufreq interface can safely be
enabled in the same kernel. This simplifies the transition to the newer
interface. Only minor updates are needed in order to allow this to be
done.

into dyn9-47-18-140.beaverton.ibm.com:/home/sridhar/BK/lksctp-2.5.45

Fix:
 - Makefile using obj-m directly, rather than subsituting the "m"
 - compiler breakage against older versions of gcc
 - adds some lacking return statements that gcc didn't catch
 - removes some 2.4 compatibility stuff
 - RTT calculation
 - puts the timeouts in terms of HZ rather than assuming HZ==100

A supplement to manfred's patch; remove copy_segments, release_segments
and even forget_segments from all architectures (except x86-64 since
Andi wants to do that seperately):

Did the changes that created this line actually build for anyone?
:-)

mbcache should be too. 

into home.transmeta.com:/home/torvalds/v2.5/linux

into home.transmeta.com:/home/torvalds/v2.5/linux

This patch changes how media-change is detected to use a mechanism more
similar to what 'popular' OSes use.

The motive for this change is that more and more emulated-SCSI devices
(sbp2, usb-storage, etc) don't support START_STOP unless they need it.
Other OSes won't send a START_STOP unless the device reports NOT_READY,
indicating that it needs an explicit command to start up.

One could argue that these devices are out-of-spec, but they are so common
that they basically define the de facto spec.

Basically, any device that needs a START_STOP should still get it, but ones
that don't need it won't.

The i386 LDT code had it's own set of arch hooks (??_segments), I've
replaced most of them with the mmu context hooks in a previous patch.
The attached patch completes that change: replace release_segments with
destroy_context.

The patch is part of the -ac kernels in 2.4.  The patch breaks x86-64,
Andi Kleen promised to send you the corresponding
s/release_segments/destroy_context/ patch.

Cleaning simplified by descending down in aicasm when cleaning.

Fixed firmware build, someone made a spelling mistakei (aix -> aic).

No longer include Rules.make.

Made the *docs targets work after the restructuring of the kbuild files.

Fix cleaning up after make htmldocs, there are some directories
that needs to be deleted in that case.

This patch updates the p4-clockmod.c driver to correctly manage
HyperThreading-enabled Pentium IVs as well as those models which do
not support HyperThreading - thanks to Venkatesh Pallipadi for
explaining cpu_sibling_map to me. Additionally, an EXPORT_SYMBOL
was missing. (spotted by Marc-Christian Petersen - thanks!)

Update to the latest parport_gsc in the PA tree.

Some misc updates:
 - adapt our config.in changes to arch/parisc/Kconfig
 - general Makefile updaes for the new build system
 - remove asm-parisc/gsc.h in favour of asm-parisc/io.h
 - Alan-approved fix for the loff_t problem
 - Define POLLREMOVE like other architectures.
 - irq handling updates from Grant Grundler

x86 doesn't evaluate the argument to flush_dcache_page so this compilation
problem has gone overlooked:

SOM is the file format used for HPUX binaries.

This huge patch moves a bunch of drivers from arch/parisc/kernel to
drivers/parisc and adds some new drivers in drivers/parisc.

Some might argue that HPUX already has quite enough of a personality.

Build fixes, PA64 fixes, some new hpux syscalls, VFS fixes.

into home.transmeta.com:/home/torvalds/v2.5/linux

M68k: Remove obsolete cruft