AC97 Codec Core
added ALC655 entry (compatible with ALC650).

CS4281 driver,RME32 driver,RME96 driver,CS46xx driver,NM256 driver
- fixed compile warnings with cast for memcpy_fromio/toio.
- use copy_to_user_fromio() in proc output.

Documentation,SB drivers,YMFPCI driver,ALS4000 driver,AZT3328 driver
CMIPCI driver,ENS1370/1+ driver,ES1968 driver,Intel8x0 driver
VIA82xx driver
- removed joystick control from the card control API.
  added joystick (or joystick_port) module option instead.
- updated documents for this joystick fix.
- moved resource management for ALS4000 from sb-common header
  to the als4000 local code.

Generic drivers,MPU401 UART,ALSA Core,ALS100 driver,AZT2320 driver
CMI8330 driver,DT019x driver,ES18xx driver,OPL3SA2 driver
Sound Galaxy driver,Sound Scape driver,AD1816A driver,AD1848 driver
CS4231 driver,CS4236+ driver,PC98(CS423x) driver,ES1688 driver
GUS Classic driver,GUS Extreme driver,GUS MAX driver
AMD InterWave driver,Opti9xx drivers,ES968 driver,SB16/AWE driver
SB8 driver,Wavefront drivers,CMIPCI driver,VIA82xx driver,YMFPCI driver
- fixed the boot parameters with long ints for non-intel architectures.
- added get_option_long() for parsing the parameter.

Intel8x0 driver
Added mpu_port initialization from the kernel command line

EMU10K1/EMU10K2 driver
Peter Zubaj <pzad@pobox.sk>:
- redesigned the default DSP routing of audigy1/2 boards.
  the normal PCM output is sent through 'Stereo Mix', while
  the independent pcm streams can be attenuated by 'PCM Front',
  'PCM Rear', and 'PCM Center/LFE' volumes.

OPL3,Raw OPL FM,ES1968 driver
removed obsolete __SND_OSS_COMPAT__.

Sound Scape driver
Chris Rankin <rankincj@yahoo.com> - use #define rather than value for the microcode size

VIA82xx driver
removed a wrong entry for gigabyte mobos.

USB generic driver
Clemens Ladisch <clemens@ladisch.de>:

- add support for M-Audio OmniStudio MIDI

Memalloc module
- fixed the compilation without PCI support.
  added ifdef CONFIG_PCI around preallocate_cards().

Documentation,PCMCIA Kconfig
- added CONFIG_ISA restriction to vxpocket and vxp440 drivers.

USB generic driver
Clemens Ladisch <clemens@ladisch.de>:

- fix Edirol comment
- use special macros for Yamaha devices
- add support for Yamaha MOTIF-R, CVP-204, CVP-206, CVP-208, CVP-210,
  PSR-1100, PSR-2100, PSR-K1, EZ-250i, MOTIF ES 6, MOTIF ES 7,
  MOTIF ES 8, CS1D, DSP1D, ACU16-C, NHB32-C, DM1000, 01V96

VIA82xx driver
- clean up the rate lock routine.
- added another gigabyte mobo entry.

ALSA Core,Timer Midlevel,ALSA sequencer,PPC DACA driver
PPC Tumbler driver
- check rootfs before calling request_module() to avoid annoying
  error messages at the boot time.

Timer Midlevel,ALSA sequencer
Clemens Ladisch <clemens@ladisch.de>:

- fixed timer resolution calculations
  Some functions assumed that timer->hw.resolution is in Hz, while it's
  actually in ns/tick.

Documentation,VIA82xx driver
- added dxs_support=4 option.  no VRA is used for DXS channels in this case.
- fixed the quirk for ASUS A7V8-X.
- added the quirk for Gigabyte mobo.
- removed the error message in codec_valid().

VIA82xx driver
- fixed the misuse of long pointer for getting the int value in
  boot parameter.

PCM Midlevel
Simplified snd_pcm_update_hw_ptr*() functions

AC97 Codec Core
fixes by James Courtier-Dutton <James@superbug.demon.co.uk>:

- fixed the wrong detection of SPDIF output.  SPDIF-out is enabled
  on all chip revisions.
- fixed the ac97 codec name shown in proc file, using ac97->id.

VIA82xx driver,AC97 Codec Core
- fixed typos in the last change to snd_ac97_set_rate().
  the correct flag to check is ac97->scaps.
- removed dxs_fixed=1 on VIA8233A (for SPDIF).
- added quirks for ASUS A7V8-X and MSI KT4V.

AC97 Codec Core
fixed snd_ac97_set_rate() to accept surround and LFE sample rates, too.

EMU10K1/EMU10K2 driver
use the standard control names for RCA and optical spdif on audigy.

ICE1712 driver
Moved spdif.setup_rate to snd_ice1712_set_pro_rate() function

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

This fixes an oops that can occur if JFS is used as the root filesystem.

Writes to a device node may cause a ->write_inode to be called during a
read-only mount.  JFS needs to check for NULL log in jfs_flush_journal. 

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

Also, make sure NET_RX_DROP is returned if we did not accept the
packet.

In implementations that use no socket locking, such as RAW sockets,
once we queue the SKB to the socket another cpu can remove the SKB
from the socket queue and free up the SKB making the skb->len access
touch freed memory.

Based upon a report from Burton Windle, kernel bugzilla #937

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

Also add some ServerWorks-specific tweaks.

into redhat.com:/spare/repo/libata-2.5

All the users of this function in the SCSI tree call it with the host
lock held.  With the new list traversal code, it was trying to take
the lock again to traverse the list.

Fix it to use the unlocked version of list traversal and modify the
header comments to make it clear that the lock is expected to be held
on calling it.

Noted by Harald Welte (laforge@netfilter.org)

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

I've been looking at enforcing lifetime phases for SCSI devices
(primarily to try to get the mid layer to offload as much of the device
creation and hotplug pieces as it can).

I've hijacked the sdev_state field of the struct scsi_device (formerly
this was a bitmap, now it becomes an enumerated state).

I've also begun adding references sdev_gendev into the code to pin the
scsi_device---initially in the queue function, but possibly this should
also be done in the scsi_command_get/put, the idea being to prevent
scsi_device freeing while there's still device activity.

The object phases I identified are:

1. SDEV_CREATED - we've just allocated the device.  It may respond to
internally generated commands, but not to user ones (the user should
actually have no way to access a device in this state, but just in
case).

2. SDEV_RUNNING - the device is fully operational

3. SDEV_CANCEL - The device is cleanly shutting down.  It may respond to
internally generated commands (for cancellation/recovery) only; all user
commands are errored unless they have already been queued (QUEUE_FULL
handling and the like).

4. SDEV_DEL - The device is gone. *all* commands are errored out.

Ordinarily, the device should move through all four phases from creation
to destruction, but moving SDEV_RUNNING->SDEV_DEL because of surprise
ejection should work.

It's starting to look like the online flag should be absorbed into this
(offlined devices move essentially to SDEV_CANCEL and could be
reactivated by moving to SDEV_RUNNING).

I haven't altered the similar bitmap model that scsi_host has, although
this too should probably move to an enumerated state model.

I've tested this by physically yanking a module out from underneath a
running filesystem with no ill effects (other than a slew of I/O
errors).

The obvious problem is that this kills possible user error handling, but
we don't do any of that yet.