into ppc970.osdl.org:/home/torvalds/v2.6/linux

Patch from Tony Lindgren

This patch by Tuukka Tikkanen updates the OMAP clock framework.
It also contains a patch by Juha Yrjölä to enable 216MHz rate
on 16xx.

Signed-off-by: Tony Lindgren 
Signed-off-by: Russell King

Patch from Tony Lindgren

This patch changes OMAP serial ports to use the standard 8250
autodetection.

Signed-off-by: Tony Lindgren 
Signed-off-by: Russell King

Patch from Ben Dooks

Ensure that TI OMAP systems are only offered if
the system is configured for TI OMAP.

Signed-off-by: Ben Dooks 
Signed-off-by: Russell King

Patch from Ben Dooks

Fix IDCODE for S3C2410A to add missing zero in hex number

Thanks to Russell King for pointing this out

Signed-off-by: Ben Dooks 
Signed-off-by: Russell King

Patch from Ben Dooks

Added missing exports of the functions in gpio.c

Thanks to Dimitry Andric for pointing this out

Signed-off-by: Ben Dooks 
Signed-off-by: Russell King

These are no longer necessary since MMC support is now merged.

Patch from Catalin Marinas

Versatile/AB code after splitting core.c
Versatile/PB code after splitting core.c

Patch from Catalin Marinas

Common changes for Versatile PB and AB

Patch from Catalin Marinas

Add ICS307 clock support

Accessing register index -1 causes vfp_get_double() to enter an
infinite loop.  Use VFP_REG_ZERO (value 16) and provide code to
emulate a sixteenth register which always returns 0.0

Patch from Nicolas Pitre

Fold two tests in one.

Signed-off-by: Nicolas Pitre 
Signed-off-by: Russell King

Patch from Ben Dooks

This fixes the following with s3c24xx power management:

- debugging needs UARTs enabled, to re-enabled UART clocks,
  save their state over suspend, and add this to the current
  documentation

- update the documentation on pm initialisation

- fix bug reported by Dimitry Andric where __raw_writel()
  has arguments the wrong way around

- fix typo (lower-case letter in S3C2410_GATSTUs2_OFFRESET)
  from Dimitry Andric

- apply Arnaud Patard's patch for pm call types

- move bits of resume code to use printk(KERN_DEBUG) as they
  are potentially before the UART resume, and are not critical
  if the system fails to re-start.

Signed-off-by: Ben Dooks 
Signed-off-by: Russell King

Patch from John Lenz

Similar to sa1111.c, convert the locomo_probe function to use
the platform_get_resource\platform_get_irq instead of accessing
the pdev->resources array directly.

Patch from Peter Chubb

Fix a simple typo.

Patch from Nicolas Pitre

Signed-off-by: Nicolas Pitre 
Signed-off-by: Russell King

Patch from Ben Dooks

Make addr_reg an `void __iomem *` instead of an unsigned long.

Signed-off-by: Ben Dooks 
Signed-off-by: Russell King

Patch from Ben Dooks

Fix incorrect bit masking of the wake maskes for 
IRQs EINT0 through EINT3 and IRQ_RTC

Signed-off-by: Ben Dooks 
Signed-off-by: Russell King

Patch from Matthias Burghardt

In ssp_init dev->port is not yet initialized. Thus it cannot be used as an argument for request_mem_region. This patch fixes that.

Patch from Matthias Burghardt

Adds bit definitions for PXA Power Manager Wake-Up Enable Register (PWER) to pxa-regs.h

Signed-off-by: Matthias Burghardt
Signed-off-by: Nicolas Pitre
Signed-off-by: Russell King

Add CONFIG_CPU_CACHE_VIVT and CONFIG_CPU_CACHE_VIPT and use
these to conditionalise cache_is_xxx().  This allows unnecessary
cache handling code to be removed by the compiler.

The __iomem attribute was correctly set, and trying to
remove it just causes more problems.

Too much cut-and-paste, hidden by the fact that without debugging,
"dev_dbg()" doesn't even look at its arguments.

It apparently really confuses some things (Apple keyboard
internal hub for one, but possibly others).

	This tiny bit of the last WE-17 patch was lost between me and
you. I initially decided to wait to resubmit, but Chris Wedgwood
reported that the MadWifi driver needs it. Sorry for not having pushed
harder.
	I recreated this patch, and tested with 2.6.10-rc1, and Chris
tested it with MadWifi. Would you mind pushing that up to Linus ?

Changelog :
	o remove unneeded const
	o spelling + comments
Signed-off-by: Jean Tourrilhes <jt@hpl.hp.com>
Signed-off-by: Jeff Garzik <jgarzik@pobox.com>

Experimented a bit more with mounting a bad ext2 filesystem.

An immediate crash was caused by zero EXT2_BLOCKS_PER_GROUP(sb).
The patch below (relative to 2.6.9) adds a few checks to make sure
that things we divide by are not zero.

into ppc970.osdl.org:/home/torvalds/v2.6/linux

into ppc970.osdl.org:/home/torvalds/v2.6/linux

On Thu, Nov 04, 2004 at 12:52:38PM -0800, Greg KH wrote:
> Hi,
>
> I get the following BUG in the sysfs code when I do:
> 	- plug in a usb-serial device.
> 	- open the port with 'cat /dev/ttyUSB0'
> 	- unplug the device.
> 	- stop the 'cat' process with control-C
>
> This used to work just fine before your big sysfs changes.

There is a similar problem reported by s390 people where we see parent
kobject (directory) going away before child kobject (sub-directory). It
seems kobject code is able to handle this, but not the sysfs. What could
be happening that in sysfs_remove_dir() of parent directory, we try to
remove its contents. It works well with the regular files as it is the
final removal for sysfs_dirent corresponding to the files. But in case
of sub-directory we are doing an extra sysfs_put().  Once while removing
parent and the other one being the one from when sysfs_remove_dir() is
called for the child.

The following patch worked for the s390 people, I hope same will work in
this case also.


o Do not remove sysfs_dirents corresponding to the sub-directory in
  sysfs_remove_dir(). They will be removed in the sysfs_remove_dir() call
  for the specific sub-directory.
Signed-off-by: Maneesh Soni <maneesh@in.ibm.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

The spin_unlock() in rotate_reclaimable_page() is not a sufficient memory
barrier.
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

"clear_buffer_locked()" is just a nicer name for a clear-bit, and
on x86 (and others) we don't need any expensive memory barriers
after that.

into kroah.com:/home/greg/linux/BK/driver-2.6

into kroah.com:/home/greg/linux/BK/usb-2.6

kfifo_alloc tries to round up the buffer size to the next power of two.

But it accidently uses the original size when calling kfifo_init,
which will BUG.
Acked-by: Stelian Pop <stelian@popies.net>
Signed-off-by: Martin Waitz <tali@admingilde.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>

This is a relatively small changeset, to address small nagging problems.
Andrew pointed me at the double registration specifically, so I had to do
something about it. At least now Fabio's box won't collapse if he configures
UB by mistake. Also, a few people complained that the help text was
misleading.

I have not done anything about the oops on disconnect which happens to
Martin Schlemmer. It's next. After that I can get to Peter Jones' CD
burning patch and doing resets.

- Fix double kobject registration and eventual oops on unplug if a device
  is not cooperating.
- Add a reference to usb-storage into the configuration help.
- Just upping timeouts fixes my ZIP drive.
- Max out the diag (trace) file size.
- Set capacity to zero in case the media is absent. It works in 2.4.10-rc1.
  Either Al fixed the block layer, or the whole thing was a bug in ub.c
  (and sd.c) and a big misunderstanding.
Signed-off-by: Pete Zaitcev <zaitcev@redhat.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Attached patch adds a MAINTAINER entry for the kernel event layer.
Signed-Off-By: Robert Love <rml@novell.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Looks like kobject_uevent_init is executed before netlink_proto_init and
consequently always fails.  Not cool.

Attached patch switches the initialization over from core_initcall (init
level 1) to postcore_initcall (init level 2).  Netlink's initialization
is done in core_initcall, so this should fix the problem.  We should be
fine waiting until postcore_initcall.

Also a couple white space changes mixed in, because I am anal.
Signed-Off-By: Robert Love <rml@novell.com>
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

Thanks to Serge Hallyn <serue@us.ibm.com> for pointing this out.
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>

This clarifies more of the x86 caller/callee stack ownership
issues by making the exception and interrupt handler assembler
interfaces use register calling conventions.

System calls still use the stack.

Tested with "crashme" on UP/SMP.