After the last few days of debugging, we've ended up with the caller
of the start_tx and stop_tx methods taking the per-port lock.  This
cset and the accompanying csets make the same change to some of the
other methods for consistency reasons.  Since these methods don't
contain a lot of code, it is better that they have consistent locking
rules.

This cset fixes up the enable_ms method.

After the last few days of debugging, we've ended up with the caller
of the start_tx and stop_tx methods taking the per-port lock.  This
cset and the accompanying csets make the same change to some of the
other methods for consistency reasons.  Since these methods don't
contain a lot of code, it is better that they have consistent locking
rules.

This cset fixes up the stop_rx method.

We were missing an element in the old_serial_port structure.

The following two patches seem to be needed to export the requisite
symbols needed for fully modular builds of the new serial drivers in
2.5.28.

The old form of designated initializers are obsolete: we need to
replace them with the ISO C forms before 2.6.  Gcc has always
supported both forms anyway.

From Rusty's Trivial Patch - thanks.

Trying to open a non-present port (for configuration) causes us to
to endlessly loop (by returning -ERESTARTSYS).  We should be returning
success.  This cset fixes this.

Allocate positive instead of negative line numbers when 8250.c
registers a new port with the core.  This bug could cause
registrations to erroneously fail, or oopsen when the pcmcia
serial device is ejected.

These drivers are now part of drivers/serial

the global irq-lock debugging

cpqfcTSinit.c:
  Fix usage of Scsi_Cmnd->request so it will compile.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

 - introduce new type of context-switch locking, this is a must-have for
   ia64 and sparc64.

 - load_balance() bug noticed by Scott Rhine and myself: scan the
   whole list to find imbalance number of tasks, not just the tail
   of the list.

 - sched_yield() fix: use current->array not rq->active.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

into kroah.com:/home/greg/linux/BK/pci_hp-2.5

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

No commit message

into atnf.csiro.au:/workaholix1/kernel/v2.5/rgooch-2.5

Switch to set_current_state() and move before add_wait_queue().
Updated README from master HTML file.
Fixed devfs entry leak in <devfs_readdir> when *readdir fails.

The patch below consolidates some duplicate code, reduces some
indentation, and adds a freeing of a page in mem_read() that could be left
unfreed, as far as I can see.

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

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

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

make cpqarray and cciss use these

Heading Rusty off at the pass...

This also changes and array initialiser...

get_spare recently became static and no-one told md_k.h

Sync_sbs tries to access the ->sb for the first rdev of an mddev.
This can oops as the wrong arg is given to list_entry, and also
if a define was faound to be failed, as failed devices have their ->sb
removed.  But that removal isn't necessary, so now an rdev will always
have an ->sb.

Define container_of which cast from member to struct with some type checking.

This is much like list_entry but is cearly for things other than lists.

List_entry now uses container_of.

  new vendor/device ID;
  redundant check removed from probe();

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

 The old form of designated initializers are obsolete: we need to
 replace them with the ISO C forms before 2.6.  Gcc has always supported
 both forms anyway.

Dawson Engler's Stanford Checker reported this missing unlock to
LKML 11 July (amongst "56 potential lock/unlock bugs in 2.5.8").

Found by Simon Trimmer <simon@veritas.com>: shmem_file_write
failure path duplicates kunmap, causing oops holding kmap_lock.

Trivial: vfs_link in 2.5 checks S_ISDIR first, shmem_link
need not repeat it, but test crept back in at some stage.

Martin Schwidefsky <schwidefsky@de.ibm.com> reported "Bug with shared
memory" to LKML 14 May: hang due to schedule in truncate_list_pages
called from .... shm_destroy holding shm_lock spinlock.  shm_destroy
needs that lock for shm_rmid, but it can be safely unlocked once link
from id to shp has been removed.