The keyboard maps are generated from appropriate .map files by running
loadkeys --mktable. However, there are two reasons to provide shipped
versions and use those by default

1) Not everybody has loadkeys installed.
2) As pointed out by Andries Brouwer, if changes to the tables occur in
   the kernel tree, that may require a new/recompiled version of loadkeys,
   so that the version of loadkeys required for the kernel build is
   often ahead of the installed base.

For these reasons, we provide shipped versions of the generated files and
use them unless the user explicitly asks for regenerating by uncommenting
the appropriate line in the Makefile.
 

make did normalize away the "./", so we better put the command
explicitly.

(Geert Uytterhoeven, Adam Richter and others)

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

Added the new target "help" that list the most common targets
Calls down to Documentation/Makefile to list documentation targets.
Furthermore calls down to the architecture specific Makefile
to list architecture specific targets.
So far only i386 is supporting this.

Use the provided rule for linking files and final polish.
Apart from being internally more logically structured, 
"make KBUILD_VERBOSE= bzImage" output looks much improved now as
well.

Unify zImage and bzImage generation.

Use standard Rules.make rules for compiling and assembling.

Use the Rules.make provided objcopy command and untangle piggy.o
generation.

Again, don't just add flags into $(OBJCOPY), but use the
variable $(OBJCOPYFLAGS) instead.

Some archs sneaked additional flags for ld into $(LD). This can be done
cleaner now, by just using $(LDFLAGS).

Everywhere else we use CFLAGS_<target> etc to designate special flags
for an object, so handle vmlinux the same way.

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

Some arch Makefiles use LDFLAGS to keep special flags for the final
vmlinux link. However, we'd rather use LDFLAGS along the lines of
CFLAGS, AFLAGS etc, so get rid of these special cases.

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.

    
o Provide $(obj),$(objtree) and friends in the top-level Makefile as well
  for consistency (Sam Ravnborg)
o Make $(call cmd,whatever) consistent with $(call if_changed,whatever),
  i.e. both will execute $(cmd_whatever)
o Add $(echo_target), which will print the current target in a suitable
  way for the quiet output format (i.e. target name relative to the
  top-level directory)
o Fix the dependencies for host compiled programs to work for files in
  subdirectories (missed converting them when introducing $(depfile))
o Add commands which will be useful when generating boot images.

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.