We had a dummy dependency on include/linux/compile.h, but it really caused
more trouble than benefits. It's not actually needed for the module
postprocessing, it was only put there to make sure we recognize when
gcc changed under us. However, we really can only do so much, and
the rest of kbuild won't notice a changed gcc either, so if the user replaces
gcc during a build, he just can't rely on the build doing the right thing.

The common cases are still covered, anyway. When the command to invoke
gcc changes ("CC=gcc32") we notice, and when the path to

	/usr/lib/gcc-lib/i386-redhat-linux/2.96/include/stdarg.h

changes (which luckily contains the "2.96", we'll notice and handle that,
too.

1) Remove dep from "make help", it is no longer useful
2) replace Generating with GEN when generating version.h

When a rule in the top-level Makefile includes scripts as one
of the prerequisites it inherits FORCE, and thus is always build.
include/linux/autoconf.h recently included scripts hereby forcing
split-include to be run for each compilation.

Fix all rules that lists scripts as a prerequisite but did not list FORCE.
Fixed by listing the executable needed direct.

We don't really have a nice way to say "compile this when CONFIG_FOO
is y, don't otherwise".

Alternatives are:

obj-$(subst m,,$(CONFIG_FOO)) := foo.o

or

obj-$(CONFIG_FOO)	:= foo.o
obj-m :=

or

obj-y			:= do_foo.o
do_foo-$(CONFIG_FOO)	:= foo.o

I chose the last one, though I'm not particularly happy with either.

You wouldn't expect that an innocent two-line patch would practically
destroy the entire functionality of the USB subsystem.  But that's what my
last patch did.  I didn't realize until I saw it in Greg's list of patches
forwarded to Linus; that patch includes a mistakenly unreverted prior
change.  This explains the problems I was having yesterday, and probably
also the problems a great many people are having today.

Anyway, here's the correction -- it puts things back to what they should
have been in the first place.  Greg, please apply this and send it to
Linus for his tree as soon as reasonably possible.

This is a temporary patch which should get cardbus working again.
In order to use pci_remove_behind_bridge(), we need to separately
allocate the pci_dev structures.

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

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

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

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

1) Define comma so dependency files does not include a '_' in the filename
2) Use correct path for mkspec and mkversion
3) Removed checkhelp - corresponding perl script is no longer present
4) Spelling correction (reported on lkml)

For some people (though not me), the '+' indicating that a command will
invoke a sub-make didn't propagated properly, and caused a warning.
Putting the command all into one line should fix that.

Plus some cosmetics and clean up the per_cpu check.

Alas no rave reviews on lkml, but the private feedback I have received so
far on the recent changes has been excellent. The Rhine-II is now finally
usable with via-rhine. Time to call it 1.17.

This trivial patch fixes an obvious typo. Please apply.

Bad semicolon in previous patch ([1/2]). Thanks to
Erik@harddisk-recovery.nl for spotting this.

update CPUfreq documentation, and move it to extra directory.

Update x86 drivers so that they can live with the new cpufreq governor
"userspace".

sparc64 doesn't need any change, and I'll send the corresponding patch
for ARM to Russell King.

The old /proc/sys/cpu/ - based interface is nothing else than a
cpufreq governor which decides what frequency to use within a policy
based on userspace input. So, convert this interface (and add a
corresponding sysfs file, /sys/devices/sys/cpu0/scaling_setspeed) to
become a cpufreq governor, and move it out to an extra module (which
partly explains the size of this patch).

- update the VIA Longhaul driver to use frequency table helpers and
  the advanced cpufreq driver registration interface.
- cleanup of the ACPI P-States cpufreq driver
- very small update of the core -- set 24API values ahead of the setpolicy
  call.

- switch the AMD Elan, AMD PowerNow-K6 and the Cyrix/MediaGX driver
  to use the advanced cpufreq_driver registration process
- cleanups

Fix an operator precedence bug that caused a comparison to always
return false. Patch from John Levon <levon@movementarian.org>.

into kroah.com:/home/greg/linux/BK/pci-2.5

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

Patch from Dave Hansen.

Fix simple bounding error found by some Stanford-checker type thing
to use the proper MAX_MP_BUSSES define instead of a constant.

This simple patch just makes sure the PIT code is available for NUMA-Q
(as its TSCs are not synced).

Has been tested in my tree for over a month on UP, SMP, and NUMA and
compile tested against a variety of different configs.

At the moment, there are two different switches used, irqbalance_disabled
and no_balance_irq ... each of which switches half the code off. This
patch harmonises them into one (irqbalance_disable), and uses the old
subarch stuff as a default value so that this is auto-disabled on boxes
like NUMA-Q that can't cope with it.

Also renamed no_balance_irq to NO_BALANCE_IRQ as it's really a static
defined number now, not pretending to be a switch variable any more.
Now off by default for NUMA-Q, on by default for others, but can be
disabled with the boot time flag if people desire.

Patch from Matthew Dobson

Provide a pcibus_to_cpumask function in the topology infrastructure to
access the pre-existing array.

Patch from William Lee Irwin

Inline and simplify pfn_to_nid - this is called heavily, it's a tiny
function, and makes a noticable difference in system time for kernel
compiles (sorry, lost the data). Is only used on NUMA machines.

Has been tested in my tree for over a month on UP, SMP, and NUMA and
compile tested against a variety of different configs.

translation_table could be unintialised on machines other than NUMA-Q.
You never see this, as the compiler happens to optimise it away, but
it's still a Really Bad Idea (tm). Thanks to someone whose name I have
unfortunately forgotten for pointing this out.

Has been tested in my tree for over two weeks on UP, SMP, and NUMA and
compile tested against a variety of different configs.

Patch from William Lee Irwin

This moves the node's pgdat into the node's own local memory area along
with the lmem_map.

It only touches arch/i386/mm/discontig.c - ie can only affect NUMA
machines.  Has been tested in my tree for over a month on UP, SMP, and
NUMA and compile tested against a variety of different configs.

This fixes a bug introduced in the recent scsi_scan.c reorganisation.

Without this patch, my Alpha Jensen was crashing just after detecting
its first SCSI disk.  It is now working fine.

After 12 hours of testing it looks like this problem can be
solved by the following..

into kroah.com:/home/greg/linux/BK/gregkh-2.5

I believe && is meant here, but I cannot test it. This is against 2.5.63

Against 2.5.63. I believe && is meant here, not &.

Move the USB documentation to a separate file.

Just say -ENODEV