kernel_samsung_tuna.git - kernel/samsung/tuna

	Commit message (Collapse)	Author	Age	Files	Lines
*	sparc,sparc64: unify lib/	Sam Ravnborg	2008-12-04	1	-143/+0
\| \| \| \| \| \| \| \| \| \|	o Renamed files in sparc64 to <name>_64.S when identical to sparc32 files. o iomap.c were equal for sparc32 and sparc64 o adjusted sparc/Makefile now we have only one lib/ Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: David S. Miller <davem@davemloft.net>
*	ftrace: rename FTRACE to FUNCTION_TRACER	Steven Rostedt	2008-10-20	1	-2/+2
\| \| \| \| \| \| \| \| \| \| \| \|	Due to confusion between the ftrace infrastructure and the gcc profiling tracer "ftrace", this patch renames the config options from FTRACE to FUNCTION_TRACER. The other two names that are offspring from FTRACE DYNAMIC_FTRACE and FTRACE_MCOUNT_RECORD will stay the same. This patch was generated mostly by script, and partially by hand. Signed-off-by: Steven Rostedt <srostedt@redhat.com> Signed-off-by: Ingo Molnar <mingo@elte.hu>
*	sparc64: Implement IRQ stacks.	David S. Miller	2008-08-12	1	-0/+22
\| \| \| \|	Signed-off-by: David S. Miller <davem@davemloft.net>
*	sparc64: Fix recursion in stack overflow detection handling.	David S. Miller	2008-08-12	1	-3/+14
\| \| \| \| \| \| \| \| \| \| \|	The calls down into prom_printf() when we detect an overflowed stack can recurse again since the overflow stack will be "below" the current kernel stack limit. Prevent this by just returning straight if we are on the stack overflow safe stack already. Signed-off-by: David S. Miller <davem@davemloft.net>
*	sparc64: add ftrace support.	David Miller	2008-05-23	1	-4/+54
\| \| \| \| \| \|	Signed-off-by: David S. Miller <davem@davemloft.net> Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
*	Remove obsolete #include <linux/config.h>	Jörn Engel	2006-06-30	1	-1/+0
\| \| \| \| \|	Signed-off-by: Jörn Engel <joern@wohnheim.fh-wedel.de> Signed-off-by: Adrian Bunk <bunk@stusta.de>
*	Linux-2.6.12-rc2	Linus Torvalds	2005-04-16	1	-0/+61
	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!