This converts /proc/io{mem,ports} to the seq_file interface
(single_open).

This patch fixes the incomplete data return problem of /proc/ide/triflex.
When the number of consecutive read bytes are smaller than the total
data in triflex_get_info(), the second read() returns 0.

Fixes for the 31 bit compatability layer:
 * add compat function for jiffies_to_timeval
 * convert parameters of clone system call
 * incorporate changes from setup_arg_pages to setup_arg_pages32
 * incorporate changes from do_execve to do_execve32
 * take care of nanosecond field in struct timespec
 * remove functions of old module system calls
 * add TIF_31BIT thread flag and replace S390_FLAG_31BIT with it
 * add arch_get_unmapped_area
 * add wrapper for sys_set_tid_address

Add missing/fix existing s390 relocations in the kernel module loader.

trivial s390 fixes/typos.

updates for s390 scsi support

- remove bogus header file
- add a definition for free_dma() to make scsi.c work

updates for unified netdev config

- remove duplicate questions from drivers/s390/Kconfig
- some trivial fixes to make the s390 specific options work
- new default configurations

clean up the IUCV driver

updates for compiling with gcc-3.3pre

- add -finline-limit=10000 to make it build
- drop .eh_frame elf section from vmlinux
- fix common warnings inn asm headers
- make dasd compile
- Don't warn about signed/unsigned comparisions
- fix inline syscall macros

update extable support in s390 and s390x

this makes use of the unified extable code.
for 31 bit s390, this is slightly more complicated
than the other architectures, but as long as
no one outside /arch uses search_exception_tables,
everything should work nicely

minor changes to s390 documentation

updates for s390 dasd driver

Some problems have been found in the dasd error handling code, they
are fixed by the update to dasd_3990_erp.c.

Dasd is one of only two remaining drivers that use the null
elevator instead of iosched. Appearantly, the null elevator
has some bitrot and can result in random data loss. For now,
we just don't use it.

Bug fixes for the CTC driver

also removes the bogus intparm_t typedef

updates for the channel subsystem and qdio driver

This adds the missing support for chp machine checks, i.e.
enabling or disabling a set of devices from the service element.
Some minor bugs in the driver are fixed as well.

s390 arch changes/bug fixes:
 * add sys_fadvise64 system call
 * add initialization of init_sighand
 * add support for clone option CLONE_SETTLS
 * make use of ptrace_notify
 * sig -> sighand rename
 * move ptrace_signal_deliver to the correct place
 * make eieio a memory barrier
 * fix race condition on cpu_vm_mask in __flush_tlb_mm
 * add missing KM_SOFTIRQ0, KM_SOFTIRQ1 in asm-s390x/kmap_types.h
 * add inline assmelby for _raw_write_trylock

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

Make kmod force default handlers before executing the user process.

into kernel.bkbits.net:/home/davem/net-2.5

the lane spec says the following about path switching:

10.1.2.7 Transmitting Held Frames

Once the LE_FLUSH_RESPONSE is received, the LE Client MUST
transmit any held  data frames on the new data path before
transmitting any further frames on the new path.

10.1.2.8 Switching Over Paths Without Flush

Regardless of the provisions of the rest of Section 10.1, when
switching from the old path to a new path, if an LE Client has
not transmitted a data frame to a particular LAN Destination via
the old path for a period of time greater than or equal to the
C22 Path Switching Delay, then it MAY start using the new path
without employing the Flush protocol.

the lane client in linux-atm does do this but it doesnt send the
held frames until a frame is transmitted on the vcc after the flush
has completed.  often this doesnt happen until you get an ip retransmit.
the following patch sends the held frames after the flush completes
(or the switching delay expires)

Stelian Pop reported that all signals are blocked in processes
execed from the kernel as usermode helpers.

and gid in local inode (not just remote)

 - suspend & remove for pci_socket was broken -- thanks to Paul
   Mackerras for noting this
 - to correctly initialize multiple pci_socket devices, a sock_offset is
   needed.
 - s_info doesn't need to be an array.

 - switch the Intel x86 speedstep/Pentium 4/Xeon drivers and the
   Transmeta Crusoe Longrun driver to use the advanced cpufreq_driver
   registration process
 - cleanups
 - spelling fixes (Petri Koistinen) - thanks!

Move x86 CPU_FREQ config choices to extra file & menu. (Marc-Christian Petersen)

 - Make MTRR driver compatible with 2.4/x86-64 again.  This fixes an
   endless loop in the XFree86 4.3pre server.
 - Fix the boot code that rejected earlier: rewrote early CPU detection
   and SSE is forced now
 - Always force inlining in vsyscalls

We should probably always read the vendor ID from each function
rather than assuming that it is identical to function 0.

cb_alloc() allocated a pci_dev on the stack to access PCI space.  This
is unnecessary since we have pci_bus_*_config_* functions.  Use these
functions instead.

cardbus.c uses its own names for our PCI config space functions.
Make it use our names.

read_cb_mem is only ever called with its "fn" argument set to zero.
We therefore do not need to pass it.

cb_setup_cis_mem doesn't reference the pci device.  Remove this unused
argument.

cb_config() and cb_release() are just simple dummy functions that are
only used in the internals of the PCMCIA code.  We inline them where
used.