This adds initial driverfs support to ISAPNP driver.  It was approved by
the ISAPNP maintainer (Jaroslav Kysela).

Seperates affs_sb_info from struct super_block.

Seperates hfs_sb_info from struct super_block.

Seperates shmem_sb_info from struct super_block.

	file_system_typer-related code moved from fs/super.c to
fs/filesystems.c

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

Seperates udf_sb_info from struct super_block.

Seperates isofs_sb_info from struct super_block.

I got burnt one too many time by mismatches between
the pci_pool and "real" slabs... something changed in
mm/slab.c and broke a driver, so I'm going for the real
fix this time.  Having poisoning that _works_ is a huge
help in the innards of the USB host controller drivers.

This patch gets rid of some #ifdefs and makes the pci_pool
code poison memory if CONFIG_DEBUG_SLAB is set.
The functionality has always been there, but this makes
it simpler to get at.

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

exiting heathrow_modem_enable() with a lock held.

SI_DETHREAD, plus a couple of minor fixes.

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

Remove remnants of zlib_fs.

Remove FS_REQUIRES_DEV from JFFS2. We never really used the block device anyway.

From Arnaldo Carvalho de Melo.

added NEC printer to quirks list

  
Workaround for the ATEN switches

Several functions in the serial drivers can be called from bottom
half or interrupt context. They must use the GFP_ATOMIC flag for
calls to kmalloc() and usb_submit_urb().
  
Functions which must use GFP_ATOMIC:
1. All *_callback() functions.
2. Any code which is inside a spinlock.
3. write(), throttle(), unthrottle(), which may be called by
   the line discipline in bottom half context.
  
Functions which can use GFP_KERNEL:
1. open(), close(), startup(), shutdown(), set_termios().

  
Here is a patch to add support for F5U011 to catc.c driver. The
patch has been compile tested against 2.5.6 and 2.5.7pre1
(and tested against 2.5.5-dj1) and should apply cleanly.

  I've written a patch Vojtech and I discussed for enhancing the
hiddev code to optionally provide more detailed output on read().
The old functionality is still supported by default, and in
situations where HID usage codes are unique across reports, the
old method is still preferable due to its terseness.
    
  The new method provides the ability to determine exactly which
value has changed, in cases where the HID usage codes are not  
unique.  It also provides a means to optionally receive notification
when input reports are received from the device, whether or not
any of the values in the report have changed.

  The details of the changes are as follows:
  
  - All current code behaves identically

  - A new ioctl pair HIDIOCGFLAG/HIDIOCSFLAG gets and clears
    flags on the hiddev device.                             

  - If you set the flag HIDDEV_FLAG_UREF, the read() call switches
    from reading hiddev_event structures to hiddev_usage_ref
    structures.  The change takes effect immediately, even to
    already queued events that haven't been read() yet.  Here's
    an example of enabling FLAG_UREF:                          

    {
        int flag = HIDDEV_FLAG_UREF;
        if (ioctl(fd, HIDIOCSFLAG, &flag) != 0) {
                perror("ioctl");
                exit(1);
        }
    }
  
  - With the HIDDEV_FLAG_REPORT set (which is only allowed if
    HIDDEV_FLAG_UREF is also set), there is a special uref that
    will be read() in addition to the ones corresponding to
    changes in the device state: when uref.field_index is set to
    HID_FIELD_INDEX_NONE, this uref is a notification that the
    report referred to by report_type and report_id has been
    received from the device.  This can be useful in situations
    when the notification of the arrival of a report is useful
    even if there is no change in state.

- bind to 7/1/2 alternate setting by default, to fix printing with HP
  LaserJet 1200 and 2200
- ioctls needed by the GPL user-mode IEEE 1284.4 driver which is part of
  the HP OfficeJet Linux driver (http://hpoj.sourceforge.net):
  - dynamic switching between 7/1/[123] alternate settings
  - sending HP vendor-specific channel-change-request to support
    memory card readers on HP PhotoSmart printers
  - inquire more information about the peripheral, including
    /proc/bus/usb/xx/yy linkage to get even more information
- fix apparent array overflow (by 1 entry) in usblp_probe when more than
  the maximum number of USB printers are connected
- for the 2.2 version, added MODULE_{INC,DEC}_USE_COUNT to prevent rmmoding
  of printer.o (and subsequent OOPSes) while a USB printer device is open
- cleaned up the code in a few places by consolidating duplicated code

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

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

make driverfs initialize early, so that ACPI can come alive
in a world where you can register devices. 

into tp1.ruhr-uni-bochum.de:/home/kai/kernel/v2.5/linux-2.5.config_sound.x

For some reason the ACPI people continue to make the mistake
of thinking that they are the root of the system.  Disabuse
them of that notion.

Clean up BSD accounting locking code..

The appended patch brings the fixes applied in 2.4 to shmem.c to 2.5.

In Detail:
- Add needed checks for shmem_file_write and shmem_symlink
- Add Documentation/filesystems/tmpfs.txt and adjust Config.help
- Add uid and gid mount options
- Make the error messages more user friendly

Pick up binfmt_elf.c SET_PERSONALITY() fix from 2.4.18.