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

selection depending on processor features.

handler to allow for better optimisation.

This should bring better performances as all interrupts are always run with 
clock switching enabled and the idle spinning always with the lower clock.

This also keeps the brokenness of that architecture localized while 
preserving the sanity of the common SA idle function.

Remove redundant irq_enter/irq_exit calls.

Updates the jornada720 config file to build with 2.4.17-rmk4

Ingo's highmem code.  This also helps with Riel's rmap VM, and
eliminates the slab overhead for these processors.

For more information, see:
http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2002-March/008089.html

This is updated version of patch 1002/1 . As build system in 2.5.5 kernel allows same name of .c files in different directories when computing dependencies and versioning information, the patch becomes simple. Now it just modify appropriate Makefile (in arch/arm/mach-sa1100) and exports one symbol in arch/arm/mach-sa10/pm.c)

This patch replace 1002/1.

(Hope, this is what you want Russel :)

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

system3.c

Even I do not realy use any ISA code of ALSA on my iPAQ I need it for compilation. As I build ALSA as modules, the dma_spin_lock symbol is missing.

I have seen both definitions of dma_spin_lock (in kernel/dma.c and arch/arm/kernel/dma.c) same as EXPORT_SYMBOL in kernel/ksyms.c, but I think, exporting it in arch/arm/kernel/dma.c should be better then making confusion in kernel/ksyms.c

2Russel: If you don't think this is good solution, we should discuss this in linux-arm-kernel mailing list

This patch changes PCMCIA MECR handling such that:
	- MECR is changed in one function only and atomically
	- a additional callback for boards to allow them to
	  tweak BS values on a per-socket basis

Note: I don't know wether or not tish changes are WIP or done
already. If so, please drop it and send me a note.

Changes files:
linux/drivers/pcmcia/sa1100_generic.h
linux/drivers/pcmcia/sa1100_generic.c

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

* Make matroxfb compilable with Mystique, but without G450 support.

			Petr Vandrovec

into penguin.transmeta.com:/home/penguin/torvalds/repositories/kernel/linux

Documentation/filesystems/cramfs.txt
  - remove comment about ROM size limit
  - fix up magic
  - update location of tools

fs/cramfs/README
  - add note about sorted directory entries
  - mkcramfs compile-time DO_HOLES option replaced by run-time -z option
  - update tools section
  - add note about PAGE_CACHE_SIZE possibly changing on arm and ia64

fs/cramfs/inode.c
  - statfs->f_namelen = CRAMFS_MAXPATHLEN

include/linux/cramfs_fs.h
  - add CRAMFS_MAXPATHLEN (252)
  - clarify CRAMFS_SUPPORTED_FLAGS definition

scripts/cramfs
  - directory removed, the cramfs user-space tools are now located at
    <http://sourceforge.net/projects/cramfs/>.

Here are two small compile fixes for x86-64 in 2.5.6pre2.
- Remove call to schedule_tail.
- Fix inline assembly of semaphores to work with latest gcc 3.1.

This patch adds unicode support and wants to be applied on top of the LFS
one. It uses a fake nls module to do the (little endian) unicode
translation.

This patch adds LFS and moves some smb operations into per-protocol level
structs. It wants the nls patch to applied already.

Fixes smbfs oopsing on failed nls translations and maps unknown chars to
:#### strings. Also PATHLEN vs NAMELEN mixups.

This patch enables PCI buses on nodes above node 0 for
the NUMA-Q architecture. It also enables node-directed
port/IO, and cleans up a couple of tiny things that only
affect CONFIG_MULTIQUAD.

  
the patch is against 2.5.6-pre3 and contains:
        - ethtool support;
        - using mii.h for the MII registers and constants;
        - 2 more device/vendor IDs added;

This is one of the very early steps on cleaning up the SCSI cdrom
driver.  It gets rid of directly accessing the scsi_CDs array in favour
of using the handle we get from the generic cdrom layer.  Also uses
local vars instead of many grouped scsi_CDs accesses in other places.

The gain is to get rid of the global, static array of CDROMS
in the end.

ehci-0306, iso, philips, speedups
  
      - adds preliminary highspeed ISO support
      - tweaks the driver to support the Philips EHCI
      - does less in the IRQ handler
      - avoids accessing one immutable PCI register
  
The ISO support should be enough to start writing
drivers, not that I know of any ISO devices that are
really available yet, but it's not fully cooked yet.
  
As a functional milestone, this means Linux now
handles all kinds of highspeed device I/O.  (But it
doesn't yet handle split periodic transactions, to
full or low speed devices through USB 2.0 hubs.)
    
Thanks to Rory Bolt for the non-ISO bits here!

kill all subsidiary threads in a thread group when the main thread
exits.

Features:

 - It sends the subsidiary threads SIGKILL with SI_DETHREAD.

 - Subsidiary threads doing an execve() just leave the thread group (rather
   than forcing the master thread to do an execve() which would be more POSIX
   like).

hcd-0305, periodic and pci fixup
  
      - removes the pci dependency you mentioned in the
        rh_string code (friendlier to non-PCI HCs)
      - makes code match doc (8859-1 chars, not just ascii)
      - adds sanity checking for the periodic transfer interval,
        and forces it to a power-of-two (code can leave HCDs)
      - facilitates better IRQ sharing

	- removed dependancy on net/irda header files from the driver.

 - changed printer.c to use dynamic urbs, as that is now necessary.

These are the small subset which were obviously correct.

Evgeniy Polyakov <johnpol@2ka.mipt.ru>:
	Patches check return values for request_region() and misc_register().
	This patches make janitorial project TODO list a bit smaller.

Stephen Rothwell <sfr@canb.auug.org.au>: [PATCH] APM idleing fix:

	This bug slipped back in with the need_resched() macro substitution.

atomic ops are *not* barriers any more.

Sebastian Wilhelmi <wilhelmi@ira.uka.de>: Re: Question on your "Unreliable Guide To Locking":
  > Yes, this is no longer true.  The modern assumptions are that they are
  > not barriers.