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.

1/14 definitions of CONFIG_SOUND have trivially different banners.

2/4 definitions of CONFIG_SOFT_WATCHDOG have trivially different banners.

1/3 definitions of CONFIG_PSMOUSE have trivially different banners.

1/3 definitions of CONFIG_PPP have trivially different banners.

2/6 definitions of CONFIG_PCI have trivially different banners.

2/5 definitions of CONFIG_BLK_DEV_SR have trivially different banners.