kernel.git/include/linux/ncp_fs.h, branch linux-2.6.21.y

[PATCH] mark struct inode_operations const 3

2007-02-12T17:48:46Z

Many struct inode_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

[PATCH] Move ncpfs 32bit compat ioctl to ncpfs

2006-10-01T07:39:23Z

The ncp specific compat ioctls are clearly local to one file system, so the code can better live there. This version of the patch moves everything into the generic ioctl handler and uses it for both 32 and 64 bit calls. Signed-off-by: Arnd Bergmann Signed-off-by: Petr Vandrovec Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

Move several *_SUPER_MAGIC symbols to include/linux/magic.h.

2006-09-24T15:13:19Z

Signed-off-by: Jeff Garzik

Don't include private files from user-visible part of linux/ncp_fs.h

2006-04-25T13:26:26Z

Signed-off-by: David Woodhouse

[PATCH] Make most file operations structs in fs/ const

2006-03-28T17:16:06Z

This is a conversion to make the various file_operations structs in fs/ const. Basically a regexp job, with a few manual fixups The goal is both to increase correctness (harder to accidentally write to shared datastructures) and reducing the false sharing of cachelines with things that get dirty in .data (while .rodata is nicely read only and thus cache clean) Signed-off-by: Arjan van de Ven Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

[PATCH] ncpfs: remove kmalloc wrapper

2006-01-15T02:27:12Z

Remove remaining kmalloc wrapper bits from fs/ncpfs/. Signed-off-by: Pekka Enberg Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds

Linux-2.6.12-rc2

2005-04-16T22:20:36Z

Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip!