kernel_samsung_smdk4412.git - kernel for Galaxy S3

	Commit message (Collapse)	Author	Age	Files	Lines
*	[PATCH] update 'getting sparse' info.	Dave Jones	2007-03-08	1	-3/+7
\| \| \| \| \| \| \| \|	- point to the sparse webpage - use git:// instead of rsync:// Signed-off-by: Dave Jones <davej@redhat.com> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
*	kbuild: clarify "make C=" build option	Robert P. J. Day	2006-09-25	1	-4/+4
\| \| \| \| \| \| \|	Clarify the use of "make C=" in the top-level Makefile, and fix a typo in the Documentation file. Signed-off-by: Sam Ravnborg <sam@ravnborg.org>
*	[PATCH] docs: update sparse.txt with CHECK_ENDIAN	Bob Copeland	2006-06-23	1	-15/+21
\| \| \| \| \| \| \| \| \| \|	Update the sparse documentation to omit the -Wbitwise flag example (as it is now passed by default), and document the kernel defines to enable endianness checking. Signed-off-by: Bob Copeland <me@bobcopeland.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	[PATCH] Documentation/sparse.txt: mention CF=-Wbitwise	Alexey Dobriyan	2005-11-07	1	-2/+2
\| \| \| \| \| \|	Signed-off-by: Alexey Dobriyan <adobriyan@gmail.com> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	[PATCH] documentation: sparse no longer uses bk, but git	Harald Welte	2005-09-23	1	-2/+2
\| \| \| \| \| \|	Signed-off-by: Harald Welte <laforge@netfilter.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	[PATCH] Documentation/sparse snapshot URL	Ben Dooks	2005-09-09	1	-1/+1
\| \| \| \| \| \| \| \|	The URL for Documentation/sparse is wrong now that it is in git. Signed-off-by: Ben Dooks <ben-linux@fluff.org> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	Linux-2.6.12-rc2	Linus Torvalds	2005-04-16	1	-0/+72
	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!