o Check misc_register return code
o request_region() return code checking
o graceful failure

o Check request_region result

o check request_region result
o Handle failure gracefully

Wow, someone found some new devices for this beast..

checks return codes, and sanitises resource allocation.

o  mention a quirk in the athlon smp detection
o  mark some use-once paths as __init

The usual check_region -> request_region work, plus freeing
of resources on failure path.

Odd, this is the missing half of the recent fix where we prefetched
too far. Not sure how this bit got dropped. Without it, we still prefetch
past the end of a range of memory.
Also small compiler hint microoptimisations

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

The following should allow the affected architectures to build in
2.5.19 as currently there will be two definitions of
copy_siginfo_to_user and if an architecture defines its own
siginfo_t it MUST define copy_siginfo().

This patch from Laurent Latil <laurent@latil.nom.fr> fixes a copy
and paste error.

 - Since Bartek has released finally an entierly user space based setup
   monitoring utility, we can finally remove the nonfunctional PROC code from
   the host chip drivers. We have preserved it thus far only for documentation
   purposes.

 - Use generic bus master DMA setup code. There is nothing wrong with it.

 - Make the ide-scsi code actually just allow for one device id per scsi host,
   since we are registering a host per device right now.  This prevents the
   repetitive device recognition. Well registering an SCSI host of every single
   disk out there isn't the proper thing to do. I will deal with that later
   after my visual perception recovers again from already looking too long at
   the SCSI code :-).

 - Deal properly with host specific data mapping. (Could be that solves some
   problems with the driver, which where in reality kernel data corruptions.)

 - Homogenize flag handling for ATAPI drivers.

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

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

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

into osdl.org:/home/mochel/src/kernel/devel/linux-2.5-linus

device model: Use driver_for_each_dev to unbind drivers from its devices (now that it's implemented)

- iterate over all devices a driver has, with proper locking on driver and refcounting on devices

driverfs: Remove default 'status' file: it had no useful read information, the commands it supported were minimal and probably broken and the comments were wrong.

if a direct lookup didn't work.

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

- Set interface's bus type as they're registered with core
- Set bus_id to have device number as well as interface number

- Suggestion from Andrew Morton: use set_page_dirty instead of SetPageDirty and move to commit_write, since it's not dirty yet in prepare_write
- Make we dput on file and directory removal to counter the lookup_hash when we create them

Here's a patch which does three things:

(1) It removes some dead code.
(2) It moves more code to using the new state machine
(3) It fixes a long standing bug relating to the sense data for a detached
    device.

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

We have a fair number of command line options which can be used
to pass information about the target to the kernel.  We also provide
a default command line which the kernel will use in absence of one
provided by the boot loader.  We pass the hard coded options via the
command line now.

atomic.h was generating some extra loads that aren't required.  In
addition, it was needlessly performing various tests inside the
atomic region.  This change fixes both these issues.

 - We don't need to save the CPSR.
 - Rearrange thread_info members so we can pull the fields out of
   thread_info more efficiently.
 - Allocate a couple of extra words for CPU specific context saving
   (eg, for Xscale ACC registers)
 - Always leave 8 bytes free at the top of the kernel stack.  This
   prevents the stack becoming completely empty when do_exit() is
   called from an exiting nfsd() thread, and causing the wrong
   pointer to be returned from current_thread_info()

This machine type is no longer maintained and is falling into bitrot
heaven.