kernel_samsung_smdk4412.git - kernel for Galaxy S3

	Commit message (Collapse)	Author	Age	Files	Lines
*	last driver import from 3.2.72 for now	Wolfgang Wiedmeyer	2015-10-23	1	-2/+2
\|
*	mtd: Update copyright notices	David Woodhouse	2010-08-08	1	-1/+1
\| \| \| \|	Signed-off-by: David Woodhouse <dwmw2@infradead.org>
*	mtd: afs: fix build warning	Russell King	2009-09-04	1	-1/+1
\| \| \| \| \| \| \| \| \|	drivers/mtd/afs.c:244: warning: format ‘%5d’ expects type ‘int’, but argument 4 has type ‘uint64_t’ [dwmw2: fix incorrect 'KB' too] Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Signed-off-by: Artem Bityutskiy <Artem.Bityutskiy@nokia.com> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
*	MTD/JFFS2: remove CVS keywords	Adrian Bunk	2008-06-04	1	-2/+0
\| \| \| \| \| \| \| \| \| \| \| \|	Once upon a time, the MTD repository was using CVS. This patch therefore removes all usages of the no longer updated CVS keywords from the MTD code. This also includes code that printed them to the user. Signed-off-by: Adrian Bunk <bunk@kernel.org> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
*	[MTD] replace kmalloc+memset with kzalloc	Burman Yan	2006-11-28	1	-2/+1
\| \| \| \| \|	Signed-off-by: Yan Burman <yan_952@hotmail.com> Signed-off-by: David Woodhouse <dwmw2@infradead.org>
*	[MTD] core: Clean up trailing white spaces	Thomas Gleixner	2005-11-07	1	-8/+8
\| \| \| \|	Signed-off-by: Thomas Gleixner <tglx@linutronix.de>
*	[PATCH] ARM: 2780/1: AFS partition length calculation fix	Catalin Marinas	2005-06-30	1	-14/+2
\| \| \| \| \| \| \| \| \| \| \|	Patch from Catalin Marinas This patch calculates the AFS partition length by expanding the image length information to the nearest erase block boundary. This eliminates the problems with JFFS2 erasing the footer. Signed-off-by: Catalin Marinas <catalin.marinas@arm.com> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
*	Linux-2.6.12-rc2	Linus Torvalds	2005-04-16	1	-0/+296
	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!