From: Bob Copeland <me@bobcopeland.com>
To: linux-fsdevel@vger.kernel.org
Cc: Bob Copeland <me@bobcopeland.com>
Subject: [RFC][PATCH 7/7] omfs: kbuild updates
Date: Wed, 15 Mar 2006 22:01:45 -0500 [thread overview]
Message-ID: <11424781052876-git-send-email-me@bobcopeland.com> (raw)
In-Reply-To: <11424781052948-git-send-email-me@bobcopeland.com>
This patch adds the OMFS option to Kconfig, allowing it to be built.
---
fs/Kconfig | 14 ++++++++++++++
fs/Makefile | 1 +
fs/omfs/Makefile | 7 +++++++
3 files changed, 22 insertions(+), 0 deletions(-)
create mode 100644 fs/omfs/Makefile
8067d5d256c9663c0bf80f1d3f2a2144425fd20f
diff --git a/fs/Kconfig b/fs/Kconfig
index e9749b0..a9a8101 100644
--- a/fs/Kconfig
+++ b/fs/Kconfig
@@ -356,6 +356,20 @@ config OCFS2_FS
- POSIX ACLs
- readpages / writepages (not user visible)
+config OMFS_FS
+ tristate "OMFS fs support (EXPERIMENTAL)"
+ depends on EXPERIMENTAL
+ help
+ This option provides support for the Optimized MPEG File System, an
+ extent-based filesystem using hashing created by SonicBlue for use
+ in the ReplayTV digital video recorder, and also used by the Rio
+ Karma portable music player. If you say Y here, you will be able
+ to read and write to OMFS partitions.
+
+ To compile this file system support as a module, choose M here: the
+ module will be called omfs. If unsure, say N.
+
+
config MINIX_FS
tristate "Minix fs support"
help
diff --git a/fs/Makefile b/fs/Makefile
index 1db7113..5675690 100644
--- a/fs/Makefile
+++ b/fs/Makefile
@@ -103,3 +103,4 @@ obj-$(CONFIG_HPPFS) += hppfs/
obj-$(CONFIG_DEBUG_FS) += debugfs/
obj-$(CONFIG_CONFIGFS_FS) += configfs/
obj-$(CONFIG_OCFS2_FS) += ocfs2/
+obj-$(CONFIG_OMFS_FS) += omfs/
diff --git a/fs/omfs/Makefile b/fs/omfs/Makefile
new file mode 100644
index 0000000..e52bab6
--- /dev/null
+++ b/fs/omfs/Makefile
@@ -0,0 +1,7 @@
+#
+# Makefile for OMFS filesystem
+#
+
+obj-$(CONFIG_OMFS_FS) += omfs.o
+
+omfs-objs := bitmap.o checksum.o dir.o file.o inode.o
--
1.2.1
next prev parent reply other threads:[~2006-03-16 3:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-16 3:01 [RFC][PATCH 0/7] Optimized MPEG file system Bob Copeland
2006-03-16 3:01 ` [RFC][PATCH 1/7] omfs: filesystem headers Bob Copeland
2006-03-16 3:01 ` [RFC][PATCH 2/7] omfs: inode and superblock routines Bob Copeland
2006-03-16 3:01 ` [RFC][PATCH 3/7] omfs: directory routines Bob Copeland
2006-03-16 3:01 ` [RFC][PATCH 4/7] omfs: file routines Bob Copeland
2006-03-16 3:01 ` [RFC][PATCH 5/7] omfs: bitmap / block allocation routines Bob Copeland
2006-03-16 3:01 ` [RFC][PATCH 6/7] omfs: checksumming routines Bob Copeland
2006-03-16 3:01 ` Bob Copeland [this message]
2006-03-16 4:33 ` [RFC][PATCH 0/7] Optimized MPEG file system Brad Boyer
2006-03-16 18:33 ` Bob Copeland
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=11424781052876-git-send-email-me@bobcopeland.com \
--to=me@bobcopeland.com \
--cc=linux-fsdevel@vger.kernel.org \
/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).