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

Patch by Keith Owens, ported to 2.5.

If the length of $(VERSION).$(PATCHLEVEL).$(SUBLEVEL)$(EXTRAVERSION)
exceeds 64 characters it silently corrupts the utsname data, resulting
in garbage for uname -r and problems running the kernel and modules.
Abort if KERNELRELEASE is too long.  Truncation is not good enough, it
results in ambiguous /lib/modules/`uname -r` contents.

Ensure that the date/time in uname are always in LANG=C.  Users with
other languages report that 8 bit values cause the boot messages to go
haywire.

- add comment about the vmlinux link components
- get rid of DRIVERS-y - always linking in sound/sound.o doesn't harm
- sort SUBDIRS in link order
- always use := to assign
- remove supeflous $(TOPDIR) for lib/lib.a

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

This turns the simple task pointer into a waitqueue, which is
needed for the poll() patch.

Another trivial part of a Matthew Wilcox patch.  This just
defines macros for distinguishing the differnet types of locks.

This uses page_cache_release() instead of put_page(), as it might
be a pagecache page.

This patch handles the case where copy_from_user fails (it could
have been unmapped from this address space by another thread).

This comment refers to the original implementation. Obsolete.

This switches linux/zlib.h to include zconf.h as <linux/zconf.h> instead of
just "zconf.h".

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

printing Sparc IRQ.

Generic BUS objects have to be registered before
devices assosciated with them are probed.  Therefore
subsys_initcall is inappropriate for such setups.
It does not work to use core_initcall for this because
the generic device layer bits need to be setup first too.
So we rename unused_initcall to postcore_initcall and use
this new initcall level for generic BUS object init.
This fixes bootup on Alpha, and Sparc64.  X86 was working
by what looks to be luck in link order.

HAVE_ARCH_SIGINFO_T platforms.

Kernel code should not include userspace headers. To avoid that
happening by mistake, ask gcc not to look into the usual places
when looking for headers. We still need to find gcc headers for
vararg and similar, though - achieved by the "-iwithprefix include"
which will look into <gcc-path>/include, as proposed by Russell
King.

A similar patch went into 2.4, so not much breakage expected.

Not that it matters, since it's only used with 7bit chars, but
anyway.

Remove absolute path in output of drivers/scsi/script_asm.pl
Extracted from Keith Owens' kbuild-2.5 by patch@luckynet.dynu.com.

This patch was extracted from Keith Owens' kbuild-2.5 by
patch@luckynet.dynu.com

This patch adds the following targets, which generate some configs
useful for testing - which kind should be clear from the names:

o allyesconfig
o allmodconfig
o allnoconfig
o randconfig

It also adds

o defconfig

which does the same as make oldconfig but uses the defaults for all
new options without asking.

The actual patch was done by Ghozlane Toumi, maintained in kbuild-2.5
by Keith Owens, and extracted by Sam Ravnborg and patch@luckynet.dynu.com.

For consistency, it makes a lot of sense to add -DMODULE (plus
the other special switches with CONFIG_MODVERSIONS) to .S files
which get assembled. It surely fixes an ugly workaround for
sparc64, guess we'll see if it breaks something for other archs
(I wouldn't think so, though)

For some cases, we cannot decide if a target would change just by looking
at its prequisites, i.e. it's quite likely that it remains the same
even though a prequisite changed. The updated timestamp would cause
a lot of unnecessary recompiles. In this case, we actually generate
a temporary file, compare it to the old file and only the contents
are different do overwrite the old file.

The "update-if-changed" snippet remains always the same, so let's
put it into a macro instead of duplicating it. After that change,
scripts/mkversion_h is so small that we rather put the three remaining
lines directly into the Makefile.

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

So here we are: make vmlinux/bzImage/whatever will now also build
modules as it goes. Other than that, everything works as usual.
"make modules" builds only the modules (but you shouldn't need
it anymore). If you don't want the modules built, you can
do "make KBUILD_MODULES= vmlinux/whatever" to only compile built-in
objects.

If people want it, I can also allow for "make vmlinux/whatever nomodules"
to do the same.

Also, add '  ' in Rules.make to properly align output in quiet mode.

If an object was changed to not export symbols anymore, the
corresponding stale .ver file would have been left lying around
and been picked up when generating modversions.h. 

The obvious solution to remove include/linux/modules/* at the
beginning of "make dep" is not really good, since that means
that .ver files would be regenerated unconditionally, thus causing
a lot of possibly unnecessary rebuilds.

So, instead, we build a temporary shadow tree of all export-objs
(as empty files) during the recursive "make fastdep" phase, and use 
that to generate modversions.h.

Ensure that we touch include/linux/modversions.h if any of the
.ver files changes, that's our marker to rebuild all modversions
affected files.

If KBUILD_VERBOSE is not set in the environment, have it default
to 1 (i.e. on)

Rules.make now has three targets:
o default (a.k.a first_rule): The actual build. Deciding whether
  to build built-in or modular or both is decided by
  $(KBUILD_MODULES) and $(KBUILD_BUILTIN) now, instead of using
  different targets
o fastdep: doesn't actually dependencies anymore, only generates
  modversions
o modules_install: Well, you guess what that does.

Cleaned up descending, and no more differentiating between 
$(subdir-y) and $(subdir-m). That means $(mod-subdirs) can
go away now.