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

We really need fixdep before we can compile anything...

(Pointed out by wli, and others)

The checksums are generally 32-bit (unsigned int), though they are saved
in symbol values, which may 64-bit, so we need to convert.

Pointed out by Anton Blanchard.

I fixed scripts/Makefile.modpost to handle CONFIG_MODULES but no modules
selected, but forgot scripts/Makefile.modinst

(pointed out by akpm)

close succession. However, for this once we'll just call it "inspired".

But let's decide pair the lock with an unlock anyway, even if it is
boring and "square".

Urban Widmark points out that modprobe calls system() in many
configurations, which drops privs since request_module() doesn't
set ruid and rguid.

This gets rid of exec_usermodehelper and makes everyone use
call_usermodehelper, which has a new "wait" flag.

Fix compile errors after futex merge.

A compliment is an expression of esteem, respect, affection, or
admiration.  As far as I can tell, this word does not yet have a
place in the kernel source.

A complement on the other hand, is what is meant in the following
places.

into samba.org:/home/paulus/kernel/for-linus-ppc

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

This fixes the spelling of "necessary" in 11 files, plus these other
fixes which were nearby:

 divisable -> divisible
 feild -> field
 effectivly -> effectively
 belive -> believe

This reduces the number of "nuber" by four and fixes the spelling
of necessary in one of those files.

Starting with 2.5.61, 8139too takes forever (30+ seconds) to take an
interface down.  This gets the driver back to regular fraction of a
second time.

The thread exit code assumes it can use SIGTERM to kill the driver
thread, not SIGKILL.

Remove the generated *.mod.c files in make clean.

into samba.org:/home/paulus/kernel/for-linus-ppc

Ok, this is the fixed and tested variant that also fixes the bug that
the previous trivial fix exposed.

Remove unneeded function declarations and correct /proc-directory name
for > 1 pcmcia_socket_class devices.

here's the compile fix for this breakage which appears if CONFIG_ACPI &&
!(CONFIG_CPU_FREQ_TABLE || CONFIG_CPU_FREQ_TABLE_MODULE).

This morning's fix for elv_former_request() is causing oopses all over the
place in the IO scheduler.

Jens, remember that I did try that fix a while ago, and the same happened.

I believe it has exposed a new problem at the __make_request/attempt_front_merge
level: if attempt_front_merge() actually succeeds, the wrong request gets freed
up in elv_merged_request().

It may be best to back this change out until it can be fixed up for real.

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

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

modpost did not warn on symbols which are exported but not defined
in the current module, but it should.

Also, fix a compile time warning, and have bk ignore *.mod.c files.

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

 - pci_disable_device() added in rr_remove_one() to balance
   pci_enable_device() in rr_init_one()
 - rr_timer() and rr_close() are leaking pci_map'ed memory: make them
   use rr_raz_{rx/tx}
 - error exiting path in rr_open() was balancing pci_alloc_consistent()
   with kfree().

The new reset function only waits up to 0.1 ms for the reset to complete,
instead of 10 ms. However, it introduces the use of a forced reset flag if
a chip doesn't seem cooperative. This fixes cases where until now only
reloading the driver or even rebooting the machine would bring the chip
back.

Fix the following bugs:
- after a watchdog timeout (still a common thing with the Rhine), the
  driver will fall back to half-duplex, ignoring the auto-negotiation
  results, killing performance completely until the driver is reloaded;
  fixed by clearing full_duplex in init_registers()
- driver considers only 0x200 for full-duplex option; now 0x220
- duplex code used dev->name before it's initialized; code section moved

The full_duplex and force_media related code is quite a mess, but this
minimal fix will make the most annoying problems go away. Looking at some
other code (e.g. mii.c) it seems to me the interaction between user force,
autoneg results and full_duplex/force_media is amazingly complex, so I'll
leave it at this for now.

The Tx underrun handling in the current driver is broken. The details have
been explained in a posting "VIA Rhine 1.15exp1, patch for
testing/discussion" a couple of months ago.