From: Bob Copeland <me@bobcopeland.com>
To: akpm@linux-foundation.org
Cc: hch@infradead.org, alan@lxorguk.ukuu.org.uk, miklos@szeredi.hu,
marcin.slusarz@gmail.com, linux-kernel@vger.kernel.org,
linux-fsdevel@vger.kernel.org, Bob Copeland <me@bobcopeland.com>
Subject: [PATCH 0/8] OMFS filesystem version 4
Date: Sat, 19 Apr 2008 16:37:29 -0400 [thread overview]
Message-ID: <1208637457-24969-1-git-send-email-me@bobcopeland.com> (raw)
Andrew, if you're still willing to pick this up in -mm, here's
an update that addresses the review items I received. Thanks to
everyone for their comments.
These patches 1-8 add the Optimized MPEG Filesystem, a proprietary
filesystem used by the embedded devices Rio Karma and ReplayTV
which are no longer manufactured. This filesystem module enables
people to access files on these devices.
version 4:
- rebased against 2.6.25-mm1
- converted prepare/commit_write to write_begin/_end
- killed leaks in the error paths of inode.c and dir.c
- split out data structures from omfs.h into omfs_fs.h
- dropped checksum.c and moved its method into inode.c
- added sanity checks on block numbers read from superblock
- added missing rename implementation
- added uid/umask mount options
- documented the basic FS usage & updated MAINTAINERS
version 3:
- fixed sparse warnings
- added more sanity checking in list traversals
version 2:
- removed private inode cache
- included GPL v2 notice
- rewrote omfs_count_free to use hamming weight library functions
- removed duplicated crc-itu-t
Version 1: initial post
reply other threads:[~2008-04-19 20:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1208637457-24969-1-git-send-email-me@bobcopeland.com \
--to=me@bobcopeland.com \
--cc=akpm@linux-foundation.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcin.slusarz@gmail.com \
--cc=miklos@szeredi.hu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).