This removes the timer usage in usb-storage.  This cleans up quite a bit
of the state machine and eliminates quite a few potential races.

Initialization commands and other non-data-path mechanisms use the USB core
timeout mechanism.  Anything in the data path uses the SCSI mid-layer
mechanism.

This patch consolidates quite of bit of code in the control thread to
place all the cleanup/error handling into one place.

This patch consolidates quite a bit of code for allocation/deallocation of
URBs, and removes a kmalloc() from a command path.

Removed usb-uhci-hcd.o from the list of UHCI drivers.
This allowed the logic to be cleaned up.
Removed CONFIG_EXPERIMENTAL dependancy, as it's no longer needed.

Ah, so both of the "hcd-ized" UHCI drivers have a common bug:
they've got logic to look at the USB_ASYNC_UNLINK flag and
block unless it's clear ... but the hcd framework is already
handling the synchronous behavior, so that's wrong.

Try to repeat that with the patch I've attached, which rips
out that duplicated code ... and so should at least get rid of
that oops, even if it doesn't entirely fix the timeout issue.

(Or: try with either the OHCI driver, or with the EHCI driver
through a USB 2.0 hub, if you have appropriate hardware.)

- Dave

p.s. Disclaimer about this patch:  all it does is rip out
      code and make it compile without warnings, but I've
      not tested it otherwise.  There's a possiblity it'll
      uncover latent issues on the other code path, but then
      that's exactly why we only want one unlink code path
      inside the HCDs!  So Greg, please merge anyway ...

This is the 2.5 version of that 2.4 patch I sent recently,
which makes the OHCI driver behave usably on at least
some cardbus systems when the card is just ejected without
a clean shutdown.

The last changes did trigger another latent bug in the inline assembly.
akpm noticed it because he compiles his kernels with frame pointers.

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

Uninline elv_next_request() and move it to elevator.c, where it belongs.
Because of CURRENT declaration, this actually saves lots of space.  From
Andrew.

init_rootfs() (from ramfs) doesn't appear in any header file.  I didn't
see any that looked like a good home, so lets put a prototype at the top
of fs/namespace.c.  This only use of this function is in namespace.c.

This patch makes sure the 3c509 module license is always GPL.  Currently
the MODULE_LICENSE() marco is only used when CONFIG_ISAPNP or
CONFIG_ISAPNP_MODULE is defined.  I have moved MODULE_LICENSE() to the
#ifdef MODULE section at the bottom of 3c509.c.

Same is true for the MODULE_DEVICE_TABLE() macro.

Not sure why I forgot to do this, but here is a small bit of tidying up
of some leftover parentheses from the memlist macro removal. The
parentheses are just noise and should go.

page_alloc.c does not use either slab.h or swapctl.h. This removes the
inclusion of those headers from page_alloc.c

nr_free_pages() is overly verbose. The following is perhaps clearer and
gets to the point with fewer lines of code and inside of 80 columns.

14 of our 17 architectures define sys_pause exactly the same
way.  The other three don't define it at all.  I assume glibc
translates pause() into sigsuspend() or something.

In favour of those now in kernel.h..

Three arch-determining symbols in drivers/mtd/maps/Config.in are wrong.
They have apparently been generated using the sensible pattern "CONFIG_FOO"
for an architecture "foo"; unfortunately the architectures are not sensible.

  CONFIG_SPARC should be CONFIG_SPARC32
  CONFIG_I386 should be CONFIG_X86
  CONFIG_SH should be CONFIG_SUPERH

Removed a spurious menu definition which was both a duplicate and
had no matching "endmenu".

Removed an "endmenu" for which there was no opening "mainmenu_option".

The config language is *not* shell.  The construct "[ foo ] || [ bar ]"
is legal in shell but not in the config language, where we should use
the equivalent "[ foo -o bar ]"

The format for the "choice" statement is:

  choice 'prompt' "{sub-prompt sub-symbol}*" default-value

and the following is *not* legal config language (note the
positioning of the closing double quote):

  choice 'prompt' "{sub-prompt sub-symbol}* default-value"

It only happens to work because of a combination of accidental
side effects of the current parsers:

  *   unpaired sub-words inside the 2nd word are silently ignored
  *   the missing last word is silently treated as if empty

Two symbols used in drivers/net/wan/Config.in are misspelled.

CONFIG_PPP_MULTLINK should be CONFIG_PPP_MULTILINK
CONFIG_PPP_SYNCTTY should be CONFIG_PPP_SYNC_TTY

1/2 definitions of CONFIG_PC_KEYB have trivially different banners.

1/3 definitions of CONFIG_PARPORT_1284 have trivially different banners.

1/2 definitions of CONFIG_NUMA have trivially different banners.

1/16 definitions of CONFIG_NETDEVICES have trivially different banners.

1/3 definitions of CONFIG_MODVERSIONS have trivially different banners.

1/11 definitions of CONFIG_HOTPLUG have trivially different banners.

2/10 definitions of CONFIG_CD_NO_IDESCSI have trivially different banners.

1/3 definitions of 64-bit CONFIG_BINFMT_ELF have trivially different banners.
1/3 definitions of CONFIG_BINFMT_ELF32 have trivially different banners.

1/17 definitions of CONFIG_SCSI have trivially different banners.