kernel_samsung_smdk4412.git - kernel for Galaxy S3

	Commit message (Collapse)	Author	Age	Files	Lines
*	NTFS: In attrib.c::ntfs_attr_set() call balance_dirty_pages_ratelimited()	Anton Altaparmakov	2005-10-11	1	-2/+1
\| \| \| \| \| \| \| \|	and cond_resched() in the main loop as we could be dirtying a lot of pages and this ensures we play nice with the VM and the system as a whole. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	[PATCH] gfp flags annotations - part 1	Al Viro	2005-10-08	1	-1/+1
\| \| \| \| \| \| \| \| \| \| \| \|	- added typedef unsigned int __nocast gfp_t; - replaced __nocast uses for gfp flags with gfp_t - it gives exactly the same warnings as far as sparse is concerned, doesn't change generated code (from gcc point of view we replaced unsigned int with typedef) and documents what's going on far better. Signed-off-by: Al Viro <viro@zeniv.linux.org.uk> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	NTFS: Fix ntfs_{read,write}page() to cope with concurrent truncates better.	Anton Altaparmakov	2005-09-19	1	-1/+1
\| \| \| \|	Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Mask out __GFP_HIGHMEM when doing kmalloc() in __ntfs_malloc() as it	Anton Altaparmakov	2005-09-12	1	-1/+1
\| \| \| \| \| \|	otherwise causes a BUG(). Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Allow highmem kmalloc() in ntfs_malloc_nofs() and add _nofail() version.	Anton Altaparmakov	2005-09-08	1	-6/+42
\| \| \| \| \| \| \| \| \| \| \|	- Modify fs/ntfs/malloc.h::ntfs_malloc_nofs() to do the kmalloc() based allocations with __GFP_HIGHMEM, analogous to how the vmalloc() based allocations are done. - Add fs/ntfs/malloc.h::ntfs_malloc_nofs_nofail() which is analogous to ntfs_malloc_nofs() but it performs allocations with __GFP_NOFAIL and hence cannot fail. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	Linux-2.6.12-rc2	Linus Torvalds	2005-04-16	1	-0/+62
	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!