From: David Mosberger <davidm@napali.hpl.hp.com>

The cache_sizes array needs to be NULL terminated, otherwise an oversized
kmalloc request runs off the end of the table.

Now that sparc64 is using gcc-3.x we can disallow gcc-2.91, etc.

Documentation/Changes already says 2.95.3, which is working fine for me.

With this change, we no longer require that per-cpu data definitions be
initialised.  That was a workaround for a bug in older gccs.  So remove the
build infrastructure which was checking for that.

Also, mention that nfs-utils-1.0.3 is required.  It isn't required yet, but
will be once we enable larger dev_t: there is an interface for exportfs which
passes dev_t's into the kernel which breaks with larger dev_t.  That
interface is old, deprecated and is not used in nfs-utils-1.0.3.

The wait_on_buffer() debug code is generating false warnings when called from
__block_prepare_write().  It is legal to wait on a zero-ref buffer when its
page is locked.  The page lock keeps try_to_free_buffers() away.

This debug code hasn't found any bugs yet.

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

must never be dereferenced directly. Make that clear in the
attribute.

magic C promotion to silently do so for us.

was the first file tested with my type checker with the anal
pointer attribute checking turned on.

user space access functions. This allows the type checker
to check proper usage.

checking, these end up being no-ops, but they get enabled
by the type checker as special address_space attributes.

There is a stunning bug.

Previously, it was done automatically by the `reti' isntruction upon
returning from the kernel, but that doesn't do the correct thing in
various cases, for instance if there's a context switch, or a softirq.

Allows for the non standard cascade