emove IOSAPIC address and GSI base from external interrupt
registration interfaces.  This lets us remove acpi_find_iosapic(),
which is functionally similar to find_iosapic().

Make pcat_compat a system property, not a per-IOSAPIC property.

	and reformat to make it fit in 100 columns.

	Keith Owens.

This patch has been running inside SGI for 2 months.  It
handles kernel stacks with multiple struct pt_regs, as found
while debugging the kernel.

I had to apply the patch below to build with CONFIG_NUMA.

	fsys_gettimeofday() patch.

This version executes in around 300 cycles on Itanium I (down from 900
or so for the original version), and so can be said to have
microsecond precision.

	invalid values.

Here is the patch that matches the changes I made for RHAS w.r.t
perfmon and the O(1) scheduler. This fixes the deadlocks we were
seing in RHAS and therefore on 2.5 as well.

The key change is that SIGPROF notifications are now delivered
in the perfmon kernel exit handler (called from entry.S).
At that point, we know none of the runqueue locks are held.

I have run the same test suite I used on RHAS overnight and no
sign of deadlocks.

into tiger.hpl.hp.com:/data1/bk/lia64/to-linus-2.5

	incomplete (as a result of a faulting mandatory RSE load).

Part of the bounds checking bugs found by the Stanford checker.

The 4 fixes below have been acked by their maintainers.

Move the definition of version[] down to where __initdata has been defined.

Patch from Joel Becker <Joel.Becker@oracle.com>

The task_struct->sig -> task_struct->signal bits.

Mikulas Patocka <mikulas@artax.karlin.mff.cuni.cz> points out a bug in
ll_rw_block() usage.

Typical usage is:

	mark_buffer_dirty(bh);
	ll_rw_block(WRITE, 1, &bh);
	wait_on_buffer(bh);

the problem is that if the buffer was locked on entry to this code sequence
(due to in-progress I/O), ll_rw_block() will not wait, and start new I/O.  So
this code will wait on the _old_ I/O, and will then continue execution,
leaving the buffer dirty.

It turns out that all callers were only writing one buffer, and they were all
waiting on that writeout.  So I added a new sync_dirty_buffer() function:

	void sync_dirty_buffer(struct buffer_head *bh)
	{
		lock_buffer(bh);
		if (test_clear_buffer_dirty(bh)) {
			get_bh(bh);
			bh->b_end_io = end_buffer_io_sync;
			submit_bh(WRITE, bh);
		} else {
			unlock_buffer(bh);
		}
	}

which allowed a fair amount of code to be removed, while adding the desired
data-integrity guarantees.

UFS has its own wrappers around ll_rw_block() which got in the way, so this
operation was open-coded in that case.

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

This removes lots of annoying problems trying to prevent both modules
from being loaded, and also shares quite a bit of code.
CONFIG_AGP3 will disable AGP3 mode operation of KT400s.

Based upon information from VIA, this also adds a bunch of placeholder
entries that will get filled in over time when they have been proven
to work with the code with no extra modification.

  
The AGP3 spec allows for >1 AGP bus. This is the first of several patches
from Jeff Hartmann towards a context-using agp_bridge, by replacing
agp_bridge.foo accesses with agp_bridge->foo accesses. For now, there
should be no functional differences, as there is still only a single
agp_bridge_data struct defined.