This updates the ADB driver and the three low-level ADB bus adaptor
drivers used on powermacs.  The files affected are all in
drivers/macintosh; they are adb.c, macio-adb.c, via-cuda.c and
via-pmu.c.

The main changes in this patch are:

- Remove the use of global cli/sti and replace them with local cli/sti,
  spinlocks and semaphores as appropriate.
- Use DECLARE_WORK/schedule_work instead of tq_struct/schedule_task.
- Improvements to the PMU interrupt handling and sleep/wakeup code.

clean up RPC client's RTO estimator.

the new RPC RTO estimator has some jiffies wrap problems.

fix up the last remaining static struct initializers in the RPC client and
portmapper.

TCP connect semantics now assume the rpciod is already running, so there
is no longer a need to bump the rpciod semaphor when connecting or closing
an RPC over TCP transport socket.

smaller patch that removes unused RPC cruft.

remove some definitions and declarations that are no longer used.

The RPC clnt struct has a cl_flags field with one bit defined (in an NFS
header, no less).  no one ever sets the flag, so remove flag, field, and
test in NFSv2 XDR routines that check for the flag.

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

Most arches seem to pull in mm.h in implictly, but at least m68knommu
needs it explicitly.

cpufreq: Intel Coppermines -- the saga continues.

The detection process for speedstep-enabled Pentium III Coppermines is
considered proprietary by Intel.  The attempt to detect this capability
using MSRs failed.

So, users need to pass the option "speedstep_coppermine=1" to the kernel
(boot option or parameter) if they own a SpeedStep capable PIII
Coppermine processor.  Tualatins work as before.

I don't see any connection between the stack limit and scheduling.  So I
think _STK_LIMIT is better defined in <linux/resource.h> than in
<linux/sched.h>.

The only place STK_LIM is used is in <asm/resource.h>, which only gets
included by <linux/resource.h>, so no change in #includes is necessary.

I've never seen any of those errors, so I guess its okay to convert them
to BUG_ONs.  It makes code look better.

This corrects DocBook formatting errors in the journalling API
documentation which stopped a "make psdocs" from working

  Changeset
  	     willy@debian.org|ChangeSet|20021016154637|46581

in linux 2.5 changed the name of .exit.text to .text.exit.

Unfortunately, one change got missed.  Fix.

This fixes the sample shellscripts given in the comments of
drivers/char/random.c.

The scripts save and restore random seeds for /dev/random across
reboots.

Again, uncovered in PPC compile.

The duplicate line was introduced by Al's
   [PATCH] (1/5) beginning of getattr series.
patch and is still present in 2.5.45.

Labeled elements are not a GNU extension but part of C99.

warning: implicit declaration of function `smp_local_timer_interrupt'

 When I was searching for prototype for set_bit() I found IMHO wrong doc
entries in include/asm-i386/bitops.h.

This is the 2nd version Torben did, basically the same as the one from
yesterday but with symbolic tune defines instead of more magic numbers.
I think the feature is good to have, and it would even allow good ide
performance even for an unsupported chipset as long as the bios sets the
timings right.

From Torben Mathiasen.

Lets just make the default fifo_batch count 16. I see a slight slope in
throughput, but the various interactiveness improvements are worth it,
imho. Plus this gets Andrew of my back, he's been lobbying for this for
a while.

Right now we have one type of barrier in the block layer, and that is
used mainly for making sure that the io scheduler doesn't reorder
requests when we don't want it to.  We also need a flag to tell the io
scheduler and low level queue that this is a barrier.  So basically two
needs:

o software barrier, prevents the io scheduler from reordering
o hardware barrier, driver must prevent drive from reordering

So this patch gets rid of REQ_BARRIER and instead adds REQ_SOFTBARRIER
and REQ_HARDBARRIER.

o Correct printk() format, from Marcelo Roberto Jimenez
o Check for NULL address in cdrom_newpc_intr() and bail

Label in wrong place.

Ensure that we can still flush out a minimum number of read, write,
and commit requests if memory gets low.

nfs_find_request() needs to be called every time we schedule a write
on the page cache. Currently it is implemented as a linked list which
needs to be traversed completely in the case where we don't already
have a pending write request on the page in question.

The following patch adopts the new radix tree, as is already used in
the page cache. Performance change is more or less negligeable with
the current hard limit of 256 outstanding write requests per mount.

However when I remove this limit then the old nfs_find_request()
actually results in a 50% reduction in speed on my benchmark test
(iozone with 4 threads each writing a 512Mb file on a 512Mb Linux
client against a Solaris server on 100Mbit switched net). With this
patch, the result for the same benchmark is a 50% increase in speed.

The following patch adds a simple ->writepages method that interprets
the extra information passed down in Andrew's writeback_control
structure, and translates it into nfs-speak.

It also adds a backing_dev_info structure that scales the readahead in
terms of the rsize. Maximum readahead is still 128k if you use 32k
rsize, but it is scaled down to 4k if you use 1k rsize.

Stub out put_dirty_page and setup_arg_pages for !CONFIG_MMU and add
free_arg_pages that frees all arg pages (noop for CONFIG_MMU)