Below a patch removing the list of sense codes from usb/storage/debug.h
since the same list is already found in scsi/constants.c.
This also brings this list up to date with SCSI-3.

The patch below cleans up some SCSI stuff.

The main purpose is to avoid trying to read the partition table
of a removable disk when the drive has told us that no media
are present. (Right now we try to read a 4K block and fail and
retry and fail, and give an I/O error on the first sector,
then try to read the second sector and fail and retry ...)

Unused fields  sector_bit_size  and  sector_bit_shift  in
struct scsi_disk were removed. The field  has_part_table
(that has nothing to do with partition tables) was
renamed to  has_been_registered . The field  ready  was
renamed to  media_present .
The overly long  sd_init_onedisk()  was split up.

When we notice that no media are present anymore, the
partitions are removed from /proc/partitions, but the
drive remains, with size 0.

A future patch will remove the field  capacity  - there are
all too many places where capacities are stored - but the
present patch is large enough already.

There is also a quite independent patch in scsi_error.c
(yesterday someone had an infinite loop retrying to read
bad media) - this patch honours the SCpnt->retries.
In case you applied this already, just ignore the scsi_error.c part.

Also some "Overrides for Emacs" were removed.

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

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

	- remove call to check_region 
	- check the result of request_region
	- call release_region if something goes wrong afterwards during driver initialisation.

I don't have this hardware so I can't verify if it works (compilation checked only).  

[janitor] update the atarilance Ethernet driver for VME Lance cards on the Atari to check the result of request_irq and exit in case of error.

Patch is also available at the following URL
        http://www.chez.com/wstinson/linux/kernel/patch-net-atari

I don't have this hardware to check for myself

	1) check the status of call to request_region 
	2) and return an error in case of problem.

I don't have this hardware so compilation checked only.

[janitor] update the comx-hw-comx wan driver to remove call to check_region and check the status of call to 
request_region instead.

I don't have this hardware so compilation checked only. 

        1) check the status of call to request_region 
        2) and return an error and release the interrupt held in case of problem.

(In my first attempted patch for this driver I had forgotten to release the interrupt.)

I don't have this hardware so compilation checked only.

to 
	1) check result of calls to request_region and handle failure to allocate region resource
	2) add and use an extra label "Failure1" which frees the region resource
	in case of device driver initialisation error later on
       
I don't have this hardware so changes not tested. 

        1) check the status of call to request_region 
        2) and return an error in case of problem.

Note that a call to check_region still remains in this driver (in subroutine check_s508_conflicts). 

I don't have this hardware so compilation checked only.

        1) remove call to check_region and use request_region instead checking the return value 
        2) release region resource in case of driver initialisation error

I don't have this hardware so compilation checked only.

        1) remove call to check_region 
        2) check the status of call to request_region 
        3) and return an error in case of problem.

and returns -EFAULT in case not all data was copied. Patch also changes the return code
of stl_getserial() from void to int in order to return error code in case of failure.

I don't have this hardware so compilation checked only.

1) checks the result of copy_to_user and 
2) returns -EFAULT in case not all data was copied. 

I don't have this hardware so compilation checked only.

	1) checks the result of copy_XX_user and returns -EFAULT in case not all data was copied. 
	2) Patch changes the return code of stl_getserial() from void to int in order to return error code in case of failure.
	3) Patch also fixes two instances of the uninitialised string name being used on request_region calls

I don't have this hardware so compilation checked only.

	1) check the result of copy_from_user 
	2) return -EFAULT in case not all data was copied
	3) release resources in case of failure

	o [CORRECT] Make discovery expiry work properly for non default
		discovery period/timeout

	        <Following patch from Shimizu Takuja/Gerhard Bertelsmann>
	o [FEATURE] Dongle driver for ActiSys 200L hardware
	        <Following patch from Leung/me>
	o [FEATURE] Dongle driver for Mobile Action MA600 hardware

o [CORRECT] Fix two bugs found by the Stanford checker in IrCOMM

	o [FEATURE] Update various comments to current state
	o [CORRECT] Handle properly failure of URB with new speed
	o [CORRECT] Don't test for (self != NULL) after using it (doh !)
	o [FEATURE] Other minor cleanups

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

* add preliminary 8169 gige support (ifdef'd out)
* support several diagnostic ethtool ioctls
* do not write to legacy 8139 registers we never use

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

This patch adds support for the Aiptek 8000U driver to the kernel tree.

	- moved the firmware download to probe() time

- added calc_num_ports() ability to determine the number of actual
  ports the device has on the fly.  This should help out with some
  of the Palm and Sony devices.

	- added calc_num_ports() callback so that driver can override the
	  fixed num_ports value after querying the device.
	- split startup() callback into probe() and attach() in anticipation
	  of the driverfs api changes
	- probe() is called before the usb_serial structure is set up,
	  and can be used to download firmware to a device, and other
	  early initialization.
	- attach() is called after the usb_serial structure is completely
	  setup, allowing the device to create private structures, and
	  have full access to the device.

In both preempt_schedule in sched.c and resume_kernel in entry.S, it is
possible to return with need_resched set and thus a pending preemption
but not service that preemption for some time.

Consider:

	- return from schedule() to preempt_schedule
	- interrupt occurs, sets need_resched
	- we cannot preempt since preempt_count = PREEMPT_ACTIVE
	- back in preempt_schedule, set preempt_count = 0

Now we again can preempt, but we will not.  Instead we return and
continue executing.  On the next interrupt, we will redo the whole
fiasco which is a waste since we could of reentered schedule while we
were there.  Worse, if we acquire a lock before the next interrupt we
can potentially delay the pending reschedule a very long time.  This is
not acceptable.

The solution is to check for and loop on need_resched on resume_kernel
and preempt_schedule like schedule itself does.

Two big ouches in x86 entry.S:

(1) Up until 2.5.20, we were not properly reading the irq_stat
    and bh_count values from the right CPU.  Brian Gerst sent you
    a patch to fix this.  This raises the question: why was this not
    a problem?  Seems we do not need this check at all as having a
    nonzero irq_star or bh_count implies having a nonzero preempt_count,
    which we test for above.  Thus this patch removes those tests and
    the related defines.

(2) What if it is possible to preempt even with interrupts disabled?
    Turns out it is.  Consider if we take an exception (say, for a
    TLB miss) and enter resume_kernel and preempt.  Even if interrupts
    are disabled, an exception can occur and end up in resume_kernel.
    We need to check to make sure interrupts are not off, to ensure
    we are not coming off an unmasked exception.

Even with the added check from issue #2, we have less code after #1 so
we can walk away with a bugfix and an optimization here. ;)

Thanks to George Anzinger, with whom I actually had #2 bite me, and who
helped with these issues.

 - Realize that the only place where ata_do_taskfile gets used is ide-disk.c
   move it and its "friends' over there.

 - Unify the do_request method for disk devices. This saves quite a lot of code.

 - Make task_muin_intr and task_in_intr use the same busy status checks on
   entry.

 - Unfold get_command at the single only place where it's used.

 - Add missing __ata_end_request on kill_rq path.

 - Rename udma_tcq_taskfile() to udma_tcq_init to make the code look like to
   normal udma_init. Revert the logics of udma_init and it's
   implementations to mirror that of udma_tcq_init().

 - Fix a tiny bug in pmac_udma_init() where it was reporting the wrong value up
   on failure.

 - Revert the logics of udma_start(). It's called from udma_init context.
   Realize that it is always returning ide_started. Make it self and the
   implementations of it return void.

 - Implement the assertion that the lock is already held, if we run
   ata_status_poll.

 - The usual host chip code load from Bartomiej onierkiewicz.  Fortunately
   I'm able to check the sis5513 fixes on a life system.

   More serious stuff... for IDE 88:

	- implement ata_best_pio_mode() in ata-timing.c
	  (play safer than driver's config_chipset_for_pio())

	- replace config_chipset_for_pio() by ata_best_pio_mode()
	  in host chips drivers
	  (trivial for hpt34x.c, hpt366.c and serverworks.c,
	   non-trivial for cmd64x.c and sis5513.c)

	- set PIO also for (U)DMA modes in cmd64x_tune_chipset()
	  (cmd64x.c)

	- fix bug in setting PIO0-2 for devices also supporting PIO3/4
	  (sis5513.c)

	- misc cleanups

 - Rename XXX_do_request back do do_request. This was just tmporary tagging.

 - Move ata_taskfile() call down to the ide-disk request handler.c, which is the
   only place needing it. Rename ata_taskfile to ata_do_taskfile().  This
   allowed us to implement the assertion that ata_do_taskfile() will be only
   called with the channel lock already held.

 - fix lock initialization  for device tree handling. Well I would be lucky if
   it would be just a device tree like in Solaris.  But after studying the code
   which goes in right now it appears to develop quite fast in to a "just in
   case" and "ad-hoc" inferface mess we have already in /proc. Shit!

   Look for example at the initialization of a device struct. First we have a
   name to the directory encompassing the device and the immediately we fill in
   the georgeous name field - which is enterly unnecessary.

 - Pull locking out from the device type drivers do_request handlers.  This
   allowed us to remove the draddy unlocking on entry to start_request.

   Much more of host controller rigister acces on crutial code paths is
   now covered by the queue access lock.