Mark the API functions accessed by other drivers with EXPORT_SYMBOL() and
make the remaining functions static.

This patch fixes up some lose ends left over from the last x86-64 jumbo merge.

 - make it compile again. ia32_ioctl was referencing IDE ioctls that got
   remove in a merge race
 - Use the memset/FXRSTOR way to initialize the FPU, as discussed.
 - Fix semctl/shmctl ABI (thanks to Andreas Schwab)
 - Other minor fixes.

  This fixes compile errors.  It has been tested with a weekend of Bonnie++ 8GB
runs on a RAID0 setup at the OSDL.  This was built against and tested on 2.5.8
and applies cleanly to 2.5.9.

  LSI told me they have a version 2.0 of the driver in development but
it would be really nice to have the dang thing working now ;-)

Fix a few spelling mistakes in documentation (arch/i386/boot/setup.S,
Documentation/sysrq.txt).

Move BKL into the fs-specific write_super()'s.

As we discussed some time ago, here is a patch for the SEM_UNDO change
that can be applied to linux-2.5.9.

warnings for proper usage.

No object-code changes, but removes warnings from the stricter
typechecking.

Now it really works (I tried).

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

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

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

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

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

As a result of the recent BKL removal in notify_change, nfsd_symlink
downs the inode semaphore twice (the first time is in fh_lock).

fixed a few times too many already ;)

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

- Make the ide-cd driver usable again in DMA mode by adapting it to the TCQ
   related request handling changes and fixing some other minor stuff related to
   this. This patch is ugly like hell I know. Cleanup will follow separately.
   It was hard enough to make this going agian at all.

in /etc/kernel-config, and only if that fails in the architecture-
specific defconfig.

USB fix documentation bug

 After some source investigations I discovered a harmless mistake:
 The description of the  usb_control_msg(...) function says
 it returns 0, or less than 0 if an error occured, but
 the usb_internal_control_msg returns length, which is sometimes >0
 (success) or <0 if error.

was already done based on CPU capabilities at run-time

Oh, and for non-x86 platforms with interesting pci
mapping, this tweak to one new routine would be
important in a particular error path I've yet to see ... :)

It fixes problems with interrupt transfers, which I think that
nobody else has run into (or I'd surely have heard of it :).
Looks like not many folk are using USB 2.0 hubs yet.

    - wasn't checking enough of the periodic schedule to
      detect bandwidth overcommit (would BUG out)
    - frames to uframes is rightshift 3, not 8 :)
    - properly cleans up (no oops!) after certain rare errors
      in the interrupt submit path (just my luck to hit one)
    - use that cleanup to bypass some old implementation
      shortcuts in the control and bulk submit paths
    - there are also some other minor updates/cleanups

  
  general cleanups:
  	- removed commented out function prototypes
  	- removed duplicate function prototypes
  	- removed unneeded #include
  	- added named initializers
  	- merged lots of the individual device structures into general 1, 2, and 4 port structures.

vda@port.imtp.ilyichevsk.odessa.ua: SAK messages:
  I use SAK from time to time when I have problems with hung processes.

  Sometimes it is difficult to figure out what was being killed and why.

  For example, Midnight Commander contains a bug: it holds fd#3 open to
  the tty. It prevented me from daemonizing processes (like X) - they
  died upon SAK.

  This little patch makes SAK tell whom and why it kills. Tested.

(Included in 2.4)

johnpol@2ka.mipt.ru: Re: Trivial patch for msbusmouse.c:
  > On Tue, Mar 19, 2002 at 03:22:58PM +1100, Rusty Russell wrote:
  > > Hi Russell,
  > >
  > > 	Please check this request_region() cleanup patch from Evgeniy
  > > Polyakov against 2.4 and 2.5.
  >
  > Both patches look fine, apart from the disgusting formatting being
  > different from the rest of the files.

  As you wish...

  > --
  > Russell King (rmk@arm.linux.org.uk)                The developer of
  > ARM Linux
  > http://www.arm.linux.org.uk/personal/aboutme.html


  	Evgeniy Polyakov ( s0mbre )

johnpol@2ka.mipt.ru: Re: Trivial patch for logibusmouse.c:
  > On Tue, Mar 19, 2002 at 03:22:58PM +1100, Rusty Russell wrote:
  > > Hi Russell,
  > >
  > > 	Please check this request_region() cleanup patch from Evgeniy
  > > Polyakov against 2.4 and 2.5.
  >
  > Both patches look fine, apart from the disgusting formatting being
  > different from the rest of the files.

  As you wish...

  > --
  > Russell King (rmk@arm.linux.org.uk)                The developer of
  > ARM Linux
  > http://www.arm.linux.org.uk/personal/aboutme.html


  	Evgeniy Polyakov ( s0mbre )

Rusty Russell <rusty@rustcorp.com.au>: 13) request_region check, 11-20:

Peter Chubb <peter@chubb.wattle.id.au>: make TAGS to work with bitkeeper:

  If you type, `make TAGS' in the top-level of a kernel tree that's been
  created with bk clone (or if you're using sccs to maintain your own
  copy), then the sccs control files are included in the TAGS file (sccs
  distinguishes its control files with an s. prefix rather than using a
  suffix, so the matches on '*.h' etc pick them up.)

Pavel Machek <pavel@ucw.cz>: typo in BK-usage.txt:

  Them them is not english...

Pavel Machek <pavel@ucw.cz>: Warn about ioctl collision:
  Hi!

  It is probably too late to fix it properly, but warning is better than
  nothing. (It confused the hell out of me...)
  									Pavel