linux - Linux kernel source tree

Age	Commit message (Collapse)	Author
2009-06-17	Cleanup of adfs headers	Al Viro
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2009-06-11	repair adfs ->write_inode(), switch to simple_fsync()	Al Viro
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2009-03-27	constify dentry_operations: misc filesystems	Al Viro
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2008-08-25	[PATCH] fix ->llseek() for a bunch of directories	Al Viro
	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
2007-02-12	[PATCH] mark struct inode_operations const 1	Arjan van de Ven
	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 <arjan@linux.intel.com> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
2006-12-08	[PATCH] struct path: convert adfs	Josef Sipek
	Signed-off-by: Josef Sipek <jsipek@fsl.cs.sunysb.edu> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2006-06-30	Remove obsolete #include <linux/config.h>	Jörn Engel
	Signed-off-by: Jörn Engel <joern@wohnheim.fh-wedel.de> Signed-off-by: Adrian Bunk <bunk@stusta.de>
2006-03-28	[PATCH] Make most file operations structs in fs/ const	Arjan van de Ven
	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 <arjan@infradead.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
2005-04-16	Linux-2.6.12-rc2v2.6.12-rc2	Linus Torvalds
	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!