linux.git - Linux kernel mainline tree

	Commit message (Collapse)	Author	Age	Files	Lines
*	sparc,sparc64: unify boot/	Sam Ravnborg	2008-12-04	4	-3/+142
\| \| \| \| \| \| \| \| \| \| \|	Simple unification: o renamed piggyback to _32.c/_64.c o copied content of Makefile from sparc64 to sparc and guard it o updated sparc/boot/.gitignore o deleted remaining files in sparc64/boot Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: David S. Miller <davem@davemloft.net>
*	sparc: gitignore a few files	Sam Ravnborg	2008-12-04	1	-0/+5
\| \| \| \| \| \| \| \|	With this 'git status' no longer reports any new files At least not for a sparc allnoconfig build Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: David S. Miller <davem@davemloft.net>
*	sparc: clean boot/	Sam Ravnborg	2008-12-04	1	-1/+2
\| \| \| \| \| \| \| \|	Leave all cleaning to boot/Makefile and delete zImage too when we do a 'make clean' Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: David S. Miller <davem@davemloft.net>
*	sparc: refactor Makefile	Sam Ravnborg	2008-12-04	1	-2/+2
\| \| \| \| \| \| \| \| \|	The btfixup step needs knowledge of all the .o files, but there is no need to pass them in independent variables. Simplify it to use only two variables. Signed-off-by: Sam Ravnborg <sam@ravnborg.org> Signed-off-by: David S. Miller <davem@davemloft.net>
*	sparc: Add target for a stripped kernel	Martin Habets	2008-08-24	1	-0/+6
\| \| \| \| \| \| \| \|	Add a target for a stripped kernel. This is used for the various packaging targets (*-pkg). Signed-off-by: Martin Habets <errandir_news@mph.eclipse.co.uk> Signed-off-by: David S. Miller <davem@davemloft.net>
*	sparc: remove CVS keywords	Adrian Bunk	2008-05-20	3	-3/+2
\| \| \| \| \| \| \| \|	This patch removes the CVS keywords that weren't updated for a long time from comments. Signed-off-by: Adrian Bunk <bunk@kernel.org> Signed-off-by: David S. Miller <davem@davemloft.net>
*	Linux-2.6.12-rc2v2.6.12-rc2	Linus Torvalds	2005-04-16	3	-0/+581
	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!