<feed xmlns='http://www.w3.org/2005/Atom'>
<title>kernel.git/fs/ntfs/lcnalloc.c, branch linux-2.6.13.y</title>
<subtitle>Hosts the 0x221E linux distro kernel.
</subtitle>
<id>https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.13.y</id>
<link rel='self' href='https://git.0xinfinity.dev/distro/kernel.git/atom?h=linux-2.6.13.y'/>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/'/>
<updated>2005-06-25T15:51:58Z</updated>
<entry>
<title>NTFS: Fix several occurences of a bug where we would perform 'var &amp; ~const'</title>
<updated>2005-06-25T15:51:58Z</updated>
<author>
<name>Anton Altaparmakov</name>
</author>
<published>2005-06-25T15:51:58Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=3bd1f4a173a3445f9919c21e775de2d8b9deacf8'/>
<id>urn:sha1:3bd1f4a173a3445f9919c21e775de2d8b9deacf8</id>
<content type='text'>
      with a 64-bit variable and a int, i.e. 32-bit, constant.  This causes
      the higher order 32-bits of the 64-bit variable to be zeroed.  To fix
      this cast the 'const' to the same 64-bit type as 'var'.

Signed-off-by: Anton Altaparmakov &lt;aia21@cantab.net&gt;
</content>
</entry>
<entry>
<title>NTFS: Fix compilation when configured read-only.</title>
<updated>2005-05-05T10:39:30Z</updated>
<author>
<name>Anton Altaparmakov</name>
</author>
<published>2005-03-17T10:51:33Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=53d59aad9326199ef5749c97513db498309a057e'/>
<id>urn:sha1:53d59aad9326199ef5749c97513db498309a057e</id>
<content type='text'>
- Add ifdef NTFS_RW around write specific code if fs/ntfs/runlist.[hc] and
  fs/ntfs/attrib.[hc].
- Minor bugfix to fs/ntfs/attrib.c::ntfs_attr_make_non_resident() where the
  runlist was not freed in all error cases.
- Add fs/ntfs/runlist.[hc]::ntfs_rl_find_vcn_nolock().

Signed-off-by: Anton Altaparmakov &lt;aia21@cantab.net&gt;
</content>
</entry>
<entry>
<title>NTFS: Fix sign of various error return values to be negative in</title>
<updated>2005-05-05T10:23:20Z</updated>
<author>
<name>Anton Altaparmakov</name>
</author>
<published>2005-03-09T15:18:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=43b01fda8b17b2b63e7dcdeed11c2ebba56b1fc9'/>
<id>urn:sha1:43b01fda8b17b2b63e7dcdeed11c2ebba56b1fc9</id>
<content type='text'>
      fs/ntfs/lcnalloc.c.

Signed-off-by: Anton Altaparmakov &lt;aia21@cantab.net&gt;
</content>
</entry>
<entry>
<title>NTFS: - Fix bug in fs/ntfs/attrib.c::ntfs_find_vcn_nolock() where after</title>
<updated>2005-05-05T10:20:49Z</updated>
<author>
<name>Anton Altaparmakov</name>
</author>
<published>2005-03-07T21:43:38Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=c0c1cc0e46b36347f11b566f99087dc5e6fc1b89'/>
<id>urn:sha1:c0c1cc0e46b36347f11b566f99087dc5e6fc1b89</id>
<content type='text'>
        dropping the read lock and taking the write lock we were not checking
        whether someone else did not already do the work we wanted to do.
      - Rename ntfs_find_vcn_nolock() to ntfs_attr_find_vcn_nolock().
      - Tidy up some comments in fs/ntfs/runlist.c.
      - Add LCN_ENOMEM and LCN_EIO definitions to fs/ntfs/runlist.h.

Signed-off-by: Anton Altaparmakov &lt;aia21@cantab.net&gt;
</content>
</entry>
<entry>
<title>NTFS: Fix printk format warnings on ia64. (Randy Dunlap)</title>
<updated>2005-05-05T10:11:47Z</updated>
<author>
<name>Randy Dunlap</name>
</author>
<published>2005-03-03T11:19:53Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=8907547d4b099e67762ea4891c127ea1f6dd1cb7'/>
<id>urn:sha1:8907547d4b099e67762ea4891c127ea1f6dd1cb7</id>
<content type='text'>
Signed-off-by: Randy Dunlap &lt;rddunlap@osdl.org&gt;
Signed-off-by: Anton Altaparmakov &lt;aia21@cantab.net&gt;
</content>
</entry>
<entry>
<title>NTFS: - Split ntfs_map_runlist() into ntfs_map_runlist() and a non-locking</title>
<updated>2005-05-05T09:56:31Z</updated>
<author>
<name>Anton Altaparmakov</name>
</author>
<published>2005-02-15T10:08:43Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=b6ad6c52fe36ab35d0fe28c064f59de2ba670c2a'/>
<id>urn:sha1:b6ad6c52fe36ab35d0fe28c064f59de2ba670c2a</id>
<content type='text'>
	helper ntfs_map_runlist_nolock() which is used by ntfs_map_runlist().
	This allows us to map runlist fragments with the runlist lock already
	held without having to drop and reacquire it around the call.  Adapt
	all callers.
      - Change ntfs_find_vcn() to ntfs_find_vcn_nolock() which takes a locked
	runlist.  This allows us to find runlist elements with the runlist
	lock already held without having to drop and reacquire it around the
	call.  Adapt all callers.

Signed-off-by: Anton Altaparmakov &lt;aia21@cantab.net&gt;
</content>
</entry>
<entry>
<title>NTFS: Use i_size_read() once and then use the cached value in</title>
<updated>2005-05-04T16:00:18Z</updated>
<author>
<name>Anton Altaparmakov</name>
</author>
<published>2004-11-11T12:42:00Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=db30d160cd8dfe1e53435fd76f4189778f1c728e'/>
<id>urn:sha1:db30d160cd8dfe1e53435fd76f4189778f1c728e</id>
<content type='text'>
      fs/ntfs/lcnalloc.c::ntfs_cluster_alloc().

Signed-off-by: Anton Altaparmakov &lt;aia21@cantab.net&gt;
</content>
</entry>
<entry>
<title>Linux-2.6.12-rc2</title>
<updated>2005-04-16T22:20:36Z</updated>
<author>
<name>Linus Torvalds</name>
</author>
<published>2005-04-16T22:20:36Z</published>
<link rel='alternate' type='text/html' href='https://git.0xinfinity.dev/distro/kernel.git/commit/?id=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2'/>
<id>urn:sha1:1da177e4c3f41524e886b7f1b8a0c1fc7321cac2</id>
<content type='text'>
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!
</content>
</entry>
</feed>
