kernel.git/net/rose, branch linux-2.6.21.y

[ROSE]: Socket locking is a great invention.

2007-03-12T22:53:33Z

Especially if you actually try to do it ;-) Signed-off-by: Ralf Baechle Signed-off-by: David S. Miller

[ROSE]: Remove ourselves from waitqueue when receiving a signal

2007-03-12T22:52:52Z

Signed-off-by: Ralf Baechle Signed-off-by: David S. Miller

[PATCH] sysctl: remove insert_at_head from register_sysctl

2007-02-14T16:09:59Z

The semantic effect of insert_at_head is that it would allow new registered sysctl entries to override existing sysctl entries of the same name. Which is pain for caching and the proc interface never implemented. I have done an audit and discovered that none of the current users of register_sysctl care as (excpet for directories) they do not register duplicate sysctl entries. So this patch simply removes the support for overriding existing entries in the sys_sysctl interface since no one uses it or cares and it makes future enhancments harder. Signed-off-by: Eric W. Biederman Acked-by: Ralf Baechle Acked-by: Martin Schwidefsky Cc: Russell King Cc: David Howells Cc: "Luck, Tony" Cc: Ralf Baechle Cc: Paul Mackerras Cc: Martin Schwidefsky Cc: Andi Kleen Cc: Jens Axboe Cc: Corey Minyard Cc: Neil Brown Cc: "John W. Linville" Cc: James Bottomley Cc: Jan Kara Cc: Trond Myklebust Cc: Mark Fasheh Cc: David Chinner Cc: "David S. Miller" Cc: Patrick McHardy Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] sysctl: rose: remove unnecessary insert_at_head flag

2007-02-14T16:09:55Z

The sysctl numbers used are unique so setting the insert_at_head flag serves no semantic purpose. Signed-off-by: Eric W. Biederman Acked-by: Ralf Baechle Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] remove many unneeded #includes of sched.h

2007-02-14T16:09:54Z

After Al Viro (finally) succeeded in removing the sched.h #include in module.h recently, it makes sense again to remove other superfluous sched.h includes. There are quite a lot of files which include it but don't actually need anything defined in there. Presumably these includes were once needed for macros that used to live in sched.h, but moved to other header files in the course of cleaning it up. To ease the pain, this time I did not fiddle with any header files and only removed #includes from .c-files, which tend to cause less trouble. Compile tested against 2.6.20-rc2 and 2.6.20-rc2-mm2 (with offsets) on alpha, arm, i386, ia64, mips, powerpc, and x86_64 with allnoconfig, defconfig, allmodconfig, and allyesconfig as well as a few randconfigs on x86_64 and all configs in arch/arm/configs on arm. I also checked that no new warnings were introduced by the patch (actually, some warnings are removed that were emitted by unnecessarily included header files). Signed-off-by: Tim Schmielau Acked-by: Russell King Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] mark struct file_operations const 8

2007-02-12T17:48:46Z

Many struct file_operations in the kernel can be "const". Marking them const moves these to the .rodata section, which avoids false sharing with potential dirty data. In addition it'll catch accidental writes at compile time to these shared resources. Signed-off-by: Arjan van de Ven Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[NET] ROSE: Fix whitespace errors.

2007-02-11T07:20:04Z

Signed-off-by: YOSHIFUJI Hideaki Signed-off-by: David S. Miller

[AX.25]: Fix unchecked rose_add_loopback_neigh uses

2006-12-18T05:59:14Z

rose_add_loopback_neigh uses kmalloc and the callers were ignoring the error value. Rewrite to let the caller deal with the allocation. This allows the use of static allocation of kmalloc use entirely. Signed-off-by: Ralf Baechle Signed-off-by: David S. Miller

[AX.25]: Fix unchecked rose_add_loopback_node uses

2006-12-18T05:59:13Z

Signed-off-by: Ralf Baechle Signed-off-by: David S. Miller

[AX.25]: Fix unchecked ax25_linkfail_register uses

2006-12-18T05:59:11Z

ax25_linkfail_register uses kmalloc and the callers were ignoring the error value. Rewrite to let the caller deal with the allocation. This allows the use of static allocation of kmalloc use entirely. Signed-off-by: Ralf Baechle Signed-off-by: David S. Miller