kernel_samsung_tuna.git - kernel/samsung/tuna

	Commit message (Collapse)	Author	Age	Files	Lines
*	take coda-private headers out of include/linux	Al Viro	2011-01-12	1	-2/+1
\| \| \| \|	Signed-off-by: Al Viro <viro@zeniv.linux.org.uk>
*	Coda: add spin lock to protect accesses to struct coda_inode_info.	Yoshihisa Abe	2010-10-25	1	-5/+14
\| \| \| \| \| \| \| \| \| \| \|	We mostly need it to protect cached user permissions. The c_flags field is advisory, reading the wrong value is harmless and in the worst case we hit a slow path where we have to make an extra upcall to the userspace cache manager when revalidating a dentry or inode. Signed-off-by: Yoshihisa Abe <yoshiabe@cs.cmu.edu> Signed-off-by: Jan Harkes <jaharkes@cs.cmu.edu> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
*	coda: use ilookup5	Jan Harkes	2007-07-19	1	-6/+1
\| \| \| \| \| \|	Signed-off-by: Jan Harkes <jaharkes@cs.cmu.edu> Signed-off-by: Andrew Morton <akpm@linux-foundation.org> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
*	[PATCH] mark struct inode_operations const 1	Arjan van de Ven	2007-02-12	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \|	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>
*	BUG_ON() Conversion in fs/coda/	Eric Sesterhenn	2006-03-24	1	-2/+1
\| \| \| \| \| \| \| \|	this changes if() BUG(); constructs to BUG_ON() which is cleaner, contains unlikely() and can better optimized away. Signed-off-by: Eric Sesterhenn <snakebyte@gmx.de> Signed-off-by: Adrian Bunk <bunk@stusta.de>
*	Linux-2.6.12-rc2	Linus Torvalds	2005-04-16	1	-0/+172
	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!