spilt up the Config.help file into smaller pieces

    - adds ethtool support (based on code from Brad Hards)
    - makes diagnostic level configurable (ethtool, module param)
    - fixes a minor mem_flags goof (thanks Oliver!)
    - device identifers now use devpath (stable ID) not devnum

This chunk is present in 2.4, missing in 2.5.  It
stops the loop thread from waiting on its owm buffers.

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

It's up to other architectures to worry about portability for now.

Moved i_sem down into notify_change() and out of the UMSDOS
function. Moved BKL down from notify_change into filesystems.

typo in that last patch, sorry.

This increases the max read/write size for nfsd from 8K to 32K.

This requires making NFSv2 return the right number in statfs
requests.  NFSv3 already does that.

[PATCH] PATCH 3 of 4 : knfsd : Store the fsid in the returned attributes instead of the device number

When a filesystem is exported with  fsid=  we should use that
fsid instead of the i_dev number when returning NFS attributes,
so that there is no chance of clients that depend on the filesys
id in the attributes getting confused by device numbers changing.

We only do this if the reference filehandle uses fsid to identify
the filesystem, so that a server can be converted from non-fsid= to
using fsid= without confusing active clients.

Previously we could only export FS_REQUIRES_DEV filesystems
as we need a devno to put in the filehandle.
Now that we have fsid= (NFSEXP_FSID) we don't need a devno
to put in the filehandle so we can relax this requirement.

Use symbolic names for some common size components in the response
size calculation for the NFSD.  This makes it easier to get the
numbers right and to review them.
This patch also fixes a few number for nfsv3 that were wrong.

Lets just kill this check -- it usually only catches drivers queueing
something in front of a started request on their own (such as shoving a
request sense in front of a failed packet command, for instance). So
it's either working around this detection in some drivers, or killing
it. I vote for the latter, patch attached against 2.5.8-pre1 :-)

moved the USB_STORAGE Config.help items into the drivers/usb/storage directory.

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

added a README file to explain what the different subdirectories are for.

moved class/storage/ back to storage/
created input/
orderd the makefiles and config.in menus better.

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/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

into hera.kernel.org:/home/mochel/BK/linux-2.5

more file movement cleanups.  Now handles misc drivers compiled into
the kernel corectly.

moved the host drivers help to the host directory

fixed lib Makefile problem with usb files moving
moved drivers/usb/scanner/ to drivers/usb/image/

moved some files from misc to image
cleaned up makefile some more.

says it should do - lock out preemption.

changes

moved lots of the Config.in info into the subdirectories.
fixed up the makefiles to work nicer.

- do not manually set task->state
- instead, in preempt_schedule, set a flag in preempt_count that
  denotes that this task is entering schedule off a kernel preemption.
- use this flag in schedule to jump to pick_next_task
- in preempt_schedule, upon return from schedule, unset the flag
- have entry.S just call preempt_schedule and not duplicate this work,
  as Linus suggested.  I agree.  Note this makes debugging easier as
  we keep a single point of entry for kernel preemptions.

The result: we can safely preempt non-TASK_RUNNING tasks.  If one is
preempted, we can safely survive schedule because we won't handle the
special casing of non-TASK_RUNNING at the top of schedule.  Thus other
tasks can run as desired and our non-TASK_RUNNING task will eventually
be rescheduled, in its original state, and complete happily.

This is the behavior we have in the 2.4 patches and 2.5 until
~2.5.6-pre.  This works.  It requires no other changes elsewhere (it
actually removes some special-casing Ingo did in the signal code).