This does a little optimisation, namely kill an unneeded counter
and put the members of the device descriptor structure in an order
that should be a little more efficient.

DEVICE_ID_SIZE clashes with the define in include/linux/device.h

Need asm/irq.h too...

Need asm/io.h if you want to use ioremap() et al.

- Delays or eliminates some IRQs  It'll mostly affect control
   or iso transfers, which typically have multiple TDs per URB,
   by making only the last TD generate an IRQ.

- Shortens some of the submit path that needs to run with
   IRQs disabled ... no need to use the dma_to_td hashtable.
   (Of course that path is still pretty long...)

- Gets rid of case where the ED state was confused ... now
   there's only one such state, not two.

Attached you'll find a patch for the Philips Webcam Driver version 8.7.
This is a jump from 8.5, since 8.6 never officially made it into the 2.5
series due to rapid changes and incompatabilities.

The biggest changes include (from the Changelog)

8.7

* Incorporating changes in ioctl() parameter passing
* Also changes to URB mechanism
* Updating copyright information

8.6

* Added ID's for Visionite VCS UM100 and UC300
* Removed YUV420-interlaced palette altogether (was confusing)
* Removed MIRROR stuff as it didn't work anyway
* Fixed a problem with the 'leds' parameter (wouldn't blink)
* Added ioctl()s for advanced features: 'extended' whitebalance ioctl()s,
  CONTOUR, BACKLIGHT, FLICKER, DYNNOISE.
* VIDIOCGCAP.name now contains real camera model name instead of
  'Philips xxx webcam'
* Added PROBE ioctl (see previous point & API doc)

One could get to like "KBUILD_VERBOSE=0 make" ... :)

This gets rid of a compile warning.

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".