litmus-rt.git - The LITMUS^RT kernel.

	Commit message (Collapse)	Author	Age
*	[PATCH] fs/ntfs: Conversion to generic boolean	Richard Knutsson	2006-10-01
\| \| \| \| \| \| \| \| \|	Conversion of booleans to: generic-boolean.patch (2006-08-23) Signed-off-by: Richard Knutsson <ricknu-0@student.ltu.se> Signed-off-by: Anton Altaparmakov <aia21@cantab.net> Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
*	NTFS: Improve comments on file attribute flags in fs/ntfs/layout.h.	Anton Altaparmakov	2006-03-23
\| \| \| \|	Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Add support for sparse files which have a compression unit of 0.	Anton Altaparmakov	2006-03-23
\| \| \| \|	Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: - Cope with attribute list attribute having invalid flags.	Anton Altaparmakov	2006-02-24
\| \| \| \| \| \| \| \| \|	Windows copes with this and even chkdsk does not detect or fix this so we have to cope with it, too. Thanks to Pawel Kot for reporting the problem. - Miscellaneous updates to layout.h. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Document extended attribute ($EA) NEED_EA flag. (Based on libntfs	Anton Altaparmakov	2005-10-24
\| \| \| \| \| \|	patch by Yura Pakhuchiy.) Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: $EA attributes can be both resident non-resident.	Anton Altaparmakov	2005-10-19
\| \| \| \| \| \|	Minor tidying. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Fix a 64-bitness bug where a left-shift could overflow a 32-bit variable	Anton Altaparmakov	2005-10-04
\| \| \| \| \| \|	which we now cast to 64-bit first (fs/ntfs/mft.c::map_mft_record_page(). Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Re-fix sparse warnings in a more correct way, i.e. don't use an enum with	Anton Altaparmakov	2005-09-26
\| \| \| \| \| \|	different types in it but #define the two constants instead. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Fix the definition of the CHKD ntfs record magic. It had an off by	Anton Altaparmakov	2005-09-26
\| \| \| \| \| \|	two error causing it to be CHKB instead of CHKD. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Fix sparse warnings that have crept in over time.	Anton Altaparmakov	2005-09-22
\| \| \| \|	Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Fix a bug in address space operations error recovery code paths where	Anton Altaparmakov	2005-06-25
\| \| \| \| \| \| \| \|	if the runlist was not mapped at all and a mapping error occured we would leave the runlist locked on exit to the function so that the next access to the same file would try to take the lock and deadlock. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Stamp the transaction log ($UsnJrnl), aka user space journal, if it	Anton Altaparmakov	2005-06-25
\| \| \| \| \| \| \|	is active on the volume and we are mounting read-write or remounting from read-only to read-write. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Update attribute definition handling.	Anton Altaparmakov	2005-05-05
\| \| \| \|	Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: Correct sparse file handling. The compressed values need to be	Anton Altaparmakov	2005-05-05
\| \| \| \| \| \| \| \|	checked and set in the ntfs inode as done for compressed files and the compressed size needs to be used for vfs inode->i_blocks instead of the allocated size, again, as done for compressed files. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	NTFS: - Add disable_sparse mount option together with a per volume sparse	Anton Altaparmakov	2005-05-05
\| \| \| \| \| \| \| \|	enable bit which is set appropriately and a per inode sparse disable bit which is preset on some system file inodes as appropriate. - Enforce that sparse support is disabled on NTFS volumes pre 3.0. Signed-off-by: Anton Altaparmakov <aia21@cantab.net>
*	Linux-2.6.12-rc2v2.6.12-rc2	Linus Torvalds	2005-04-16
	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!