From: Adrian Bunk <bunk@fs.tum.de>

The patch below removes #if'd kernel 2.0 code from
drivers/isdn/divert/divert_init.c.

From: Christian Borntraeger <linux@borntraeger.net>
  
This patch makes isdn_tty HZ aware.
The first change changes 3000 jiffies (now 3 seconds) to 30 seconds according to
the comment.
I dont know, if the second change (schedule_timeout(50);) has to be half a
second but this was the value used in 2.4.

Instead of having "switch (subtype)" in just about every function,
rather use separate functions and invoke the right one using
the now existing struct card_ops infrastructure.

All IRQ handlers for IPAC based cards were basically the same (not
a big surprise, since the chip is the same), so we can share
the IRQ handler.

IPAC is basically a combined HSCX/ISAC chip, so we can generate
the D- and B-channel access functions knowing how to access the IPAC.
  
For performance reasons, this happens in a macro.

Just renaming and introducing some helpers makes them look very similar
to each other..

Except for a minor performance penalty, using the same IRQ handler
for cards which used the same code anyway seems perfectly natural...

Again, just killing some duplicated code.

Same change which happened for the B-channel earlier.

This mostly finishes splitting up the multiplexing ->cardmsg.

Since we now have a per-card ops struct, use it to provide the
irq handler function, too.

Some drivers actually drive more than one specific hardware card,
instead of having "switch (cs->subtyp)" scattered around, we rather
aim at having different card_ops structures which just provide the
right functions for the hardware. Of course, this patch is only the
beginning of that separation, but allows for some cleaning already.

Linux normally uses separate callbacks instead of a multiplexing
function like "cardmsg". So start to break that into pieces.

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

This patch adds "frequency table helpers" to kernel/cpufreq.c and
updates some drivers to use them.

Most CPU frequency scaling methods only support a few static
frequencies. In these drivers a lot of duplicated code existed in the
->setpolicy and ->verify calls.

Please note that this in no way changes the behaviour of cpufreq or of
the ->setpolicy or ->verify calls. These "frequency table helpers"
aren't for drivers which either only support policies (longrun) or
really many frequency states (ARM, gx-suspmod).

Make gcc-2.91.66 happy. Noted by Andrew Morton - thanks.

Add support for mobile Pentium IV processors with stepping 7.

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

into tetrachloride.(none):/mnt/stuff/kernel/2.5/watchdog

into tetrachloride.(none):/mnt/stuff/kernel/2.5/watchdog

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

into tetrachloride.(none):/mnt/stuff/kernel/2.5/agpgart

version before looking at more complicated changes.