This patch adapts the ov511 driver to the videodev changes.  As Mark
McClelland already sent in a patch with updates this just deletes the
now obsolete code for the most part.  The unplug-while-in-use race fix
is also there.

This patch adapts the stv usb camera driver to the videodev changes and
fixes the unplug race.

This patch updates the cpia driver.

Additionally to the usual adoptions to the videodev changes done in all
drivers this patch has a few more changes:

 - some cleanups in the drivers open() function.
 - Use file->private_data to keep a pointer to the drivers private
   data.  This allows to unregister the device unconditionally in
   disconnect(), which in turn fixes some small races in case the
   device is unplugged while in use.

This is the update for the typhoon radio driver.

This is the update for the terratec radio driver.

This patch updates the sf16fm radio driver.

This patch updates the radiotrack driver.

Here comes the aztech radio driver update.

Here comes the aimslab radio driver update.

This is the cadet radio driver update.

This patch updates the gemtek and gemtek pci radio drivers.

This patch updates the maestro radio driver.

This patch updates the Maxi FM2000 Radio driver.

This patch adapts the usbvideo module to the videodev changes.  As with
all usb drivers, the unplug race fix is present here too.

The updates for the radio driver are all very similar:  The individual
open functions are gone and replaced by the video_exclusive_open/release
functions in videodev.c.  All userspace copying in the ioctl function is
gone because video_generic_ioctl handles this now.  The driver source
files all become slightly shorter because of this.

This contains some minor changes to i82092.c PCMCIA driver:
	- MODULE_DEVICE_TABLE() added;
	- request_region() and pci_enable_device() return value checks added;
	- some printk() cleanups.

	It looks like sk->num became inet_sk(sk)->num in 2.5.7-pre1,
but one of these changes was missed in net/ipv4/ipmr.c.  Here is
the patch.

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

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

In the FIT macro in ide-timing.h the argument got swapped because of a
typo. All timings generated for VIA and AMD chips are wrong because of
that. Safe, though, but slow.

This fixes it.

If I was to give this patch a name it would be:

"Vojtech Pavlik unleashed from the chains".

So credit where credit is due :-).

Anyway here follows the change log:

Mon Mar 11 23:48:28 CET 2002 ide-clean-21

- Swallow rewritten amd74xx host chip setup code from Vojtech Pavlik.  We can
   revert it easly if it turns out to be a bad thing. However the code looks
   quite sane to me. In esp. it doesn't containg that many magic numbers.

- Clean stale white spaces in ide-timing.h tirvial fix.

- Make ide_release_dma return void. It's value is never used anyway.

- Swallow more timing setup code cleanup by Vojtech Pavlik. Apply some
   cosmetics to it. Port opti621 to the new setup code.

- Kill abuse of ide_do_reset() on error return paths for atapi floppy tape and
   cd-rom devices. Just stop them. This gives better changes that defect
   removable media will not cause suddenly broken timings on hard discs
   containing system data! Even then comments in ide_do_reset() admit, that
   resetting the whole channel can have adverse effects on the second interface
   on this channel. And I have too frequently observed linux struggling on
   defect cd-rom for a far too long time to wish it to continue.

   Oh did I forget to say that the corresponding "how can I break my system fast
   and reliable" ioctl is gone as well?

   Removing it recovered the fact that the CONFIG_BLK_DEV_IDEDMA_TIMEOUT is
   completely bogous. I have removed this option therefore as well, because it's
   playing the same wrack havoc on the devices if enabled. This cat has been in
   an unfinished and *unfunctional* state anyway.

- Actually add physical suspend code to the power handling code.  Still the
   resume code isn't finished just jet. This is all subject to change at the
   point in time when we get to proper command queueing.
   I think however that Pavel will be interrested in tidding this bit up...

- Resync with 2.5.7-pre1.

Contributor: Eli Kupermann @ Intel

into mandrakesoft.com:/home/jgarzik/repo/net-drivers-2.5

coalescing, ring params, pause params, hw csum disable/enable,
scatter-gather enable/disable

* Merge support for hardware vlan accel
* Better wakeup behavior on TX completion
* dev->mtu setting fixes

* Merge several bug fixes from vger cvs
* Merge h/w VLAN support, now that API is in the main tree
* Add support for TX/RX coalescing

Separates efs_sb_info from struct super_block.

Add nfs_compare_super() and teaches nfs_get_sb() to look for existing
superblocks.

Switch NFS to separate allocation of private part of superblock,
uss explicit sget() instead of get_sb_nodev()

Export sget(9), deactivate_super(9) and set_anon_sb(9)

Switch NFS to use of NFS_SB(sb) instead of sb->u.nfs_sb.s_server

I forgot to zero out the newly allocated memory in the previous patches
for ext2 and ncpfs.

I forgot to zero out the newly allocated memory in the previous patches
for cramfs and minixfs.

Complete the ext2 superblock seperation.

Abstract access to ext2_sb_info.

Seperates ncp_sb_info from struct super_block.

  The following patch resyncs 2.5.6 with the 2.4.x series w.r.t. the
handling of the EJUKEBOX error. The latter is an NFS-specific error
that is returned by servers that support hierarchical storage: it
notifies the client that the request cannot be completed in a timely
fashion (Imagine for instance a situation where you have a cdrom
jukebox system, and the user has just requested a file on another cd).

Under these circumstances, the RFC specifies that the request should
be retried after suitable timeout during which the server will attempt
to perform whatever action is required to make the file available
again.

  The following patch fixes a bug in NFS file creation. Recently (not
sure exactly when), open_namei() was changed so that it expects
vfs_create() to always return a fully instantiated dentry for the new
file.

The following patch ensures this is done in the cases where the RPC
CREATE call does not return valid attributes/filehandles. This is
always the case for NFSv2, and can sometimes be the case for v3...