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

Also use strsep in ibmmca.c, as strtok is gone from the kernel.

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

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

parse_interface allocates the incorrect storage size for additional
altsettings (new buffer) leading to a BUG being triggered in
mm/slab.c:1453 when we do the memcpy from the old buffer to the new
buffer (writing beyond new buffer).
Patch appended, tested with an OV511 on an Intel PIIX4

Al pointed out that the current name of get_lease is extremely confusing
and I agree.

This (a) renames it to break_lease and (b) fixes a bug noticed by Dave
Hansen which could cause a NULL pointer dereference under high load.

into kroah.com:/home/linux/linux/BK/gregkh-2.5

 - removed a few #ifdefs in the main code
 - cleaned up the failure logic in initialization.

into kroah.com:/home/linux/linux/BK/pci-2.5

This removes the code from cap_sysget that fills out the capability set
being returned to userspace.  The module handles this in a policy
specific way.  This updates the dummy.c module to fill in return data
according to superuser policy, and also disables setting capabilities in
superuser policy.

sending routines don't set it up.

from "write()" is an error condition, and hang retrying.

Return EINVAL in sysfs instead.

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

These security_ops are declared like

        int (*inode_mknod) (struct inode *dir, struct dentry *dentry,
                            int mode, dev_t dev);

with a mode and a dev_t argument.

But the users mistakenly had major, minor instead of mode, dev.

Given Andi Kleen's patch that introduces of VFS-level support for
nanosecond time resolutions, we should finally be able to export the
existing NFS client level support to userland.

In order to do so, the following patch will convert all NFS private 'raw
u64' values into the kernel-supported struct timespec directly in the
xdr_encode/xdr_decode routines.

It adds support for the nanosecond field in NFS 'setattr' calls, and in
nfs_refresh_inode().

Finally, there are a few cleanups in the nfs_refresh_inode code that
convert multiple use of the NFS_*(inode) macros into a single
dereference of NFS_I(inode).

Fix numerous ALSA core compiler warnings of the type "unused variable foo"

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

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

was enabled, so split it up into "extable.c"

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

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

Since I believe kallsyms is important, this reimplements it sanely,
using the current module infrastructure, and not using an external
kallsyms script.

FYI, the previous interface was:

int kallsyms_symbol_to_address(
	const char       *name,			/* Name to lookup */
	unsigned long    *token,		/* Which module to start with */
	const char      **mod_name,		/* Set to module name or "kernel" */
	unsigned long    *mod_start,		/* Set to start address of module */
	unsigned long    *mod_end,		/* Set to end address of module */
	const char      **sec_name,		/* Set to section name */
	unsigned long    *sec_start,		/* Set to start address of section */
	unsigned long    *sec_end,		/* Set to end address of section */
	const char      **sym_name,		/* Set to full symbol name */
	unsigned long    *sym_start,		/* Set to start address of symbol */
	unsigned long    *sym_end		/* Set to end address of symbol */
	);

The new one is:
/* Lookup an address.  modname is set to NULL if it's in the kernel. */
const char *kallsyms_lookup(unsigned long addr,
			    unsigned long *symbolsize,
			    unsigned long *offset,
			    char **modname);

drivers/usb/serial/usb-serial.c in 2.5.48 fails to compile with the
following error:

drivers/usb/serial/usb-serial.c:842: dereferencing pointer to incompletetype

Is the following patch correct?

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