into raven.il.steeleye.com:/home/jejb/BK/scsi-misc-2.5

It contains one user-selectable option that does nothing but hiding the
four pcmcia drivers if not seleted (although we have an extra menu for
them!) one one that does exactly nothing.  Remove those two.

The config stanza for SCSI_ZALON was in the wrong place, so move it.
Make SCSI_NCR53C8XX conflict with SCSI_ZALON.
Give ncr53c8xx and sym53c8xx names
Fill in detach and release methods unconditionally.
Call pci_set_master() in sym53c8xx.
Both these drivers need interrupt.h, not sched.h

In get_sectorsize(), we can already sleep in scsi_wait_req().
In get_capabilities(), we can use GFP_KERNEL because it is only called
from sr_attach() which already does a GFP_KERNEL allocation.

This GFP_DMA can be GFP_KERNEL because sd_init_onedisk calls sd_spinup_disk
calls scsi_wait_req which can sleep.

dito

get it to actually compile cleanly again, switch to scsi_add_host,
remove host list walking.

imm.c: spelling
scsi.h: remove old and now incorrect comment
scsi_scan.c: remove superfluous final return
scsi_error.c: apart from similar trivialities the only change:

    If a command fails (e.g. because it belongs to a newer
    SCSI version than the device), it is fed to
    scsi_decide_disposition(). That routine must return
    SUCCESS, unless the error handler should be invoked.

    In the situation where host_byte is DID_OK, and message_byte
    is COMMAND_COMPLETE, and status is CHECK_CONDITION, there is
    no reason at all to invoke aborts and resets. The situation
    is normal. I see here UNIT ATTENTION, Power on occurred
    and ILLEGAL REQUEST, Invalid field in cdb.

    The 2.5.64 code does not return SUCCESS, but it returns the
    return code of scsi_check_sense(), and that may be FAILED
    in case we do not have valid sense.

Patch from Andreas Klein <asklein@cip.physik.uni-wuerzburg.de>

Fixes an off-by-one in ioremap() - local variable `last_addr' is *inclusive*
- it is the last byte of the mapping, not the usual (last byte + 1).

Fix an error-path memory leak in ext3_fill_super().

uninline some functions which have multiple callsites.  A 5% reduction in
text size.

Patch from "Randy.Dunlap" <randy.dunlap@verizon.net>

This patch reduces stack size in elf_core_dump() from over 0x400 (0x4a4 e.g.)
to less than 0x100 (0xb0 on a P4 with gcc 2.96).

Patch from Alex Tomas <bzzz@tmi.comex.ru>

There's a missing unlock_kernel().

Patch from Dave Hansen <haveblue@us.ibm.com>

ptes this time

Patch from Dave Hansen <haveblue@us.ibm.com>

Same thing as the __pgd_offset one, just for pmds this time to keep the
naming consistent.

Patch from Dave Hansen <haveblue@us.ibm.com>

__pgd_offset() and pgd_offset() are completely different functions.
__pgd_offset() is really just a helper to figure out which entry in a
pgd an address would fall into.   pgd_offset() does all the leg work and
actually fetches the real pgd entry.

pgd_index() is a much saner name for what __pgd_offset() does.  In fact,
we do this:
#define __pgd_offset(address) pgd_index(address)

The attached patch removes all instances of __pgd_offset and just
replaces them with pgd_index.

Compiles with and without PAE on x86.

Well I thought we were shooting down unused inodes a bit aggressively.  With
30,000 inodes total and 1000 unused, the 1000 are getting reclaimed
instantly.

shrink_icache_memory() needs to return the number of reclaimable inodes to
page reclaim, not the total number.

Patch from: Matthew Wilcox <willy@debian.org>

Reduces stack use in random.c by 350 (or maybe 700) bytes by sharing a local
array between two functions.

Patch from Patricia Gaughen <gone@us.ibm.com>

This function was recently uninlined for NUMAQ.  But it used to be a macro,
and modules need it.

Patch from Stephen Cameron <steve.cameron@hp.com>

* Fix driver to wait for firmware to indicate that it is ready.
  (Needed for PCI hotplug case, but for normal warm/cold reboot, by the
  time driver inits, firmware will already be ready.)

This driver is doing a division on a 64 bit valus which is identical to
"jiffies" and is asking for __udiv64.  Cast the 64-bit value back to long.

Patch from: Zwane Mwaikambo <zwane@linuxpower.ca>

Fix up a possible AB/BA deadlock identified by Dawson Engler's latest toy.

Patch from Trond Myklebust <trond.myklebust@fys.uio.no>

This has been floating about for a while, and fixes the oops which people
keep on reporting.

irqdesc_t.lock is taken from interrupts - it needs irq-safe locking from
process context.

Also timer_irq_works() needs to use an unsigned long to hold a jiffies value
(Kai Bankett)

General coding cleanups in io_apic.c:

- make pending_irq_balance_apicid[] static

- reorder several functions so that forward decls are not needed and so
  that `inline' actually works.

- 80 col fixes.

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

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

Russell King investigated a failure case I introduced: When booting
with "load_ramdisk=1", we use the kernel root= parameter to determine
from what device to get the contents to copy into a ramdisk and then
mount that ramdisk as root.

For the copy to work, /dev/root needs to point to the device to load the
ramdisk from.

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

Add SSP PIO driver - provides an interface for talking to
microcontrollers and such like connected to the SA1110's
SSP port.

into flint.arm.linux.org.uk:/usr/src/linux-bk-2.5/linux-2.5-rmk

Patch from Dominik Brodowski.

This patch is necessary to update the ARM drivers so that they can
live with the new cpufreq governor "userspace" (which I sent to Linus a
moment ago).

A 4 patch set from Dominik Brodowski, tested and fixed up by rmk
for ARM.

(1)

- the system3.c cpufreq notifier couldn't possibly compile before because
      cpufreq_updateminmax has been undefined for ages.
- clean up sa1100fb.c notifier to specify exactly what's left TBD.
- double #include of cpufreq.c in drivers/pcmcia/sa1100_generic.c

(2)

Split up config symbols, add help text for CPU_FREQ_PROC_INTF

(3)

- update the Integrator CPUfreq driver so that it can get along with
  cpufreq policies.
- modularize Integrator CPUfreq driver (all it did with
  !CONFIG_CPU_FREQ was to print out some debug information)

(4)

- update the SA11x0 CPUfreq drivers so that they can get along with
  cpufreq policies and governors.
- update the cpufreq core so that cpufreq_get() returns something
  sensible during the first ->setpolicy or ->target call.

Eliminate have_isa_bridge - use isa_bridge instead.
Clean up PCI bus walking.
Clean up detection of fast back to back capability.
Ensure we set the bridge control register appropriately.
Pin swizzle functions are never called with pin == 0.

This follows our existing PM interfaces.

This provides an element of core PM support to ARM, providing an APM
like user space interface, and separating the core PM support from
the SA1100 PM implementation.