He has added significant content to these files.

The code in xtLog assumes that the structures xdlistlock_t and
maplock_t are the same size, as they are overlaid.  On 64-bit
machines, this was not the case.

Ensure that the xdlistlock_t is 16 bytes in length regardless of
the size of a pointer.

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.

swsusp kind-of abused include/asm-i386/suspend.h for stuff that
belonged to arch/i386/kernel/suspend.c. This moves code where it
belongs.
									Pavel

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

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

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.

We used to force the obvious deep structure of all objects which
export symbols into a flat list in include/linux/modules. This
initially caused the restriction the no two exporting objects could
have the same name (Ever wondered why there's ksyms.c and
i386_ksyms.c?)

With the ALSA merge this restriction was mostly lifted by some hack,
but some cases still don't work right (Hi XFS). As it's much cleaner
to just use a normal tree under include/linux/modules, reflecting the
source tree, we now do just that.

Making dependencies once up front is not ideal. For one, you don't need
them initially, since when you don't have the .o file, you bet you have
to build it no matter what the dependencies say - dependencies are about
deciding when to *re*build.

There's more reasons, like:
o you don't even know which files you'll build, so you have to go over
  all files (even over drivers/{sbus,s390,...} on i386)
o generated files don't exist yet, so you cannot pick up dependencies
  on them
o even if dependencies are right initially, they change when you work on 
  your tree or patch it, and nobody will notice unless you run "make dep"
  explicitly again

Anyway, gcc knows hows to emit a correct dependency list, so we just use
that. Well, a little bit of hacking is necessary to remove the dependency
on autoconf.h and put in individual CONFIG_WHAT_EVER dependencies instead,
since otherwise changing one config option would cause everything to be
rebuilt.

I should add that I didn't come up with this all by myself, most work
is actually done in gcc and there were discussions about using -MD on
kbuild-devel way back, so I should mention Keith Owens and Michael
Elizabeth Chastain, and probably others that I forgot, so I apologize
just in case.

We source some scripts, but still pass parameters to them, e.g.

	. mk_version_h $@ $(KERNELRELEASE) $(VERSION) ...

This does not work for all kinds of /bin/sh (it does for bash, that's
why I did not notice).

The fix is easy: Just mark the scripts executable and call instead of
source them.

Unfortunately, patch(1) doesn't understand about propagating chmod.
bk does, so changing the tree isn't hard, and we introduce an explicit
chmod a+x executed during the build for propagating this change into
those trees which get "traditionally" patched up.