The subject says it all...

Contrary to other proposed patches I realized that there is
no such thing as vmalloc_dma.

This patch fixes a highmem issue with ns83820.c when used with the
pci dma fix for x86.  The patch was successfully tested on a highmem
machine with 5GB of ram and a file in high memory.  Cruft from the
pre-64 bit pci dma era is also removed.

This is the same patch as was posted against 2.4.19-pre10: pci_map_page
was missing a cast on x86, which resulted in the high 32 bits of an
address being silently discarded.  This patch fixes that by casting
the page number before multiplying it out.

hardsects array)

Courtesty of Martin Dalecki

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

into angband.namesys.com:/home/green/bk_work/reiser3-linux-2.5-test

and now the final irda offender :-).

Slowly we get there...

irttp.c was infected too.

irlmp_event was abusing __FUCTION__ too.
And of course it appears all red in my gvim as well.

irlmp abused __FUNCTION__ and the space bar as well.

irlap_frame this time. Let me guess they used emacs?!

irlap_event was abusing __FUNCTION__ too.

The irda people use shreddy editors saga continues.

irias_object missused __FUNCTION__ too.

This time for iriap_event.

- Fix improper __FUNCTION__ usage in iriap.c
- Trailing white garbage removal as well.

- Fix improper __FUNCTION__ usage in irda_device.
- Whitepsace cleanup there too.

- Fix improper __FUNCTION__ usage in af_irda.c

- Fix redundant white space usage there - I couldn't resist.

- Fix compilation warnings in cfbimgblt.c.

- Fix improper __FUNCTION__ usage in smb_debug.h.

It's all about giving the compiler a chance to coalesce
equal string constants - a good reason for the
C language standard to depricate the old semantics.

Fix improper __FUNCTION__ usage in st680 driver code,
cdc-ether.c. Fix namespace clash in cdc-ether.h

Fix improper usage of __FUNCTION__ in usb code.
Fix unpleasant results from some code formatting
editor (propably emacs) in i2c, which broke
an error message altogether.

Kill unused variables in legacy cdrom drivers,
after the janitorial patch got in.

This is fixing warnings about unused variables in
pd.c and pcd.c

This is fixing missing ; after branch label at two places.

This patch is against 2.5.21 vanilla.

 + replace __inline__ with inline.
 + use list_t intead of struct list_head (no bytes were harmed, bla.. bla..)
 + add the new list_move and list_move_tail mutators as inline functions.

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

by Sam Ravnborg

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

Tracking dependencies for .ver files isn't really different from
the dependency tracking for the other .[ois] targets we do,
so just use the normal $(call if_changed_dep) framework. That makes
speeds up re-running "make dep" a lot.

Up to now, we generated module versions for all objects which
were listed in $(export-objs).

This had one advantage: A changed .config will not affect which
.ver files are built, thus saving recompiles.

However, it is fundamentally broken. To build .ver files, we preprocess
the exporting sources - and the result can obviously depend on
the current .config. Even worse, some files generate errors when
preprocessed with the wrong .config - it doesn't matter a lot that
drivers/sbus/* will generate errors on x86, since it won't be used anyway,
but e.g. kernel/suspend.c cannot be preprocessed unless 
CONFIG_SOFTWARE_SUSPEND is set. - Up to now, we just silently ignore
these errors.

Actually, the whole point behind CONFIG_MODVERSIONS is to make sure
we don't insert modules into a kernel which was configured differently,
and as such the generation of symbols can only work when .config is
known.

So we now only generate symbols for objects which will actually be
compiled - which means less work, and enforce the kernel to be configured
before "make dep".

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

 - Add ARM version for asm/suspend.h
 - Use inline in atomic.h rather than __inline__
 - Fix up a missed superblock conversion in fs/adfs/map.c
   (hadn't been converted to use ADFS_SB())

The kbuild infrastructure in 2.5.21 uses the filename to generate a
dependency file, which is passed into gcc using -Wp,-MD,filename.
Unfortunately, the ',' in the filename is interpreted by GCC as an
argument separator for the preprocessor.  So, with a filename
foo,bar.c gcc ends up passing the three arguments "-MD", "foo" and
"bar.c" to cpp, which promptly complains.

We therefore rename these files to use an underscore instead of a
comma.

into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk

Keep track of possible targets while we add rules - Later, only
include the command lines / dependencies as needed.

E.g., when defining how to build multi-part objects listed in
$(multi-used-y) and $(multi-used-m), add $(multi-used-y,m) to 
the variable targets. At the end of Rules.make, we then include
the saved command lines for these targets (if they exist), needed
to check whether the command changed and we hence need to rebuild.

Previously, we always had put the .cmd/.d files into the local subdir
- now we put them into the directory where the target lives, like

	some/dir/target.o <-> some/dir/.target.o.cmd

It does not yet make a difference, since we always only generated
targets in the local directory anyway, but that will change with
tracking dependencies for .ver files.

We use A/CFLAGS_KERNEL by default anyway, so no need to set them
explicitly for built-in objects.

This patch doesn't change anything but the order (and some comments) in
Rules.make. The reason for that is that we use Rules.make for three
different purposes, fastdep, modules_install and the actual building.

As an example, we don't need all the dependencies and saved command lines
when installing modules, so it'll speed up this pass to only include the
rules which will actually get used.