Since we don't have mandatory mmap lock files we can lose this chunk

and clean up dependency rules (first "default" rule takes precedence)

The old form of designated initializers are obsolete: we need to
replace them with the ISO C forms before 2.6.  Gcc has always supported
both forms anyway.

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

Use ld to link the cpio archive into the image, build was broken
due to requiring a recent version of objcopy before, plus assorted
cleanups:

o Don't include arch/$(ARCH)/Makefile, export the needed arch-specific
  flags instead.
o Name the generated section consistently .init.ramfs everywhere.

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

Typo prevented ARM926 cpu enabled builds from succeeding.

This cset makes ARM serial drivers build.

Remove implementation specific header files from arch-sa1100/hardware.h
Move SA1101_[pv]2[vp] into SA-1101.h.

Move spin_unlock_irq() down one line.

Both the /proc/sys/cpu/ and /proc/cpufreq interface can safely be
enabled in the same kernel. This simplifies the transition to the newer
interface. Only minor updates are needed in order to allow this to be
done.

Fix:
 - Makefile using obj-m directly, rather than subsituting the "m"
 - compiler breakage against older versions of gcc
 - adds some lacking return statements that gcc didn't catch
 - removes some 2.4 compatibility stuff
 - RTT calculation
 - puts the timeouts in terms of HZ rather than assuming HZ==100

A supplement to manfred's patch; remove copy_segments, release_segments
and even forget_segments from all architectures (except x86-64 since
Andi wants to do that seperately):

Did the changes that created this line actually build for anyone?
:-)

mbcache should be too. 

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

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

This patch changes how media-change is detected to use a mechanism more
similar to what 'popular' OSes use.

The motive for this change is that more and more emulated-SCSI devices
(sbp2, usb-storage, etc) don't support START_STOP unless they need it.
Other OSes won't send a START_STOP unless the device reports NOT_READY,
indicating that it needs an explicit command to start up.

One could argue that these devices are out-of-spec, but they are so common
that they basically define the de facto spec.

Basically, any device that needs a START_STOP should still get it, but ones
that don't need it won't.