linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Kyungmin Park" <kmpark@infradead.org>
To: joern@logfs.org
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-mtd@lists.infradead.org
Subject: Re: [patch 8/15] fs/logfs/inode.c
Date: Fri, 4 Apr 2008 15:57:08 +0900	[thread overview]
Message-ID: <9c9fda240804032357i36e7eac0q1c639a017b27af42@mail.gmail.com> (raw)
In-Reply-To: <20080401181332.853833008@logfs.org>

>  +
>  +const struct super_operations logfs_super_operations = {
>  +       .alloc_inode    = logfs_alloc_inode,
>  +       .delete_inode   = logfs_delete_inode,
>  +       .destroy_inode  = logfs_destroy_inode,
>  +       .drop_inode     = logfs_drop_inode,
>  +       .read_inode     = logfs_read_inode,
>  +       .write_inode    = logfs_write_inode,
>  +       .statfs         = logfs_statfs,
>  +       .sync_fs        = logfs_sync_fs,
>  +};

Same reason, 'read_inode' is removed.

After some works, it can compile but there's undefined symbols.
WARNING: "swapper_space" [fs/logfs/logfs.ko] undefined!
WARNING: "add_to_page_cache_lru" [fs/logfs/logfs.ko] undefined!
WARNING: "inode_lock" [fs/logfs/logfs.ko] undefined!

Which kernel version do you use?

Thank you,
Kyungmin Park

  reply	other threads:[~2008-04-04  6:57 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-01 18:13 [patch 0/15] LogFS take five joern
2008-04-01 18:13 ` [patch 6/15] fs/logfs/file.c joern
2008-04-01 18:13 ` [patch 12/15] fs/logfs/segment.c joern
2008-04-01 18:13 ` [patch 9/15] fs/logfs/journal.c joern
2008-04-01 18:13 ` [patch 10/15] fs/logfs/memtree.c joern
2008-04-10 14:07   ` Arnd Bergmann
2008-04-11 10:37     ` Jörn Engel
2008-04-01 18:13 ` [patch 1/15] Makefiles and Kconfig joern
2008-04-07  8:28   ` Christian Borntraeger
2008-04-07  8:40     ` Jörn Engel
2008-04-08  0:30   ` Arnd Bergmann
2008-04-08  8:33     ` Jörn Engel
2008-04-08 13:41       ` Arnd Bergmann
2008-04-08 13:52         ` Jörn Engel
2008-04-01 18:13 ` [patch 8/15] fs/logfs/inode.c joern
2008-04-04  6:57   ` Kyungmin Park [this message]
2008-04-07 11:12     ` Jörn Engel
2008-04-01 18:13 ` [patch 15/15] fs/logfs/dev_mtd.c joern
2008-04-01 18:13 ` [patch 7/15] fs/logfs/gc.c joern
2008-04-01 18:13 ` [patch 4/15] fs/logfs/compr.c joern
2008-04-10 14:13   ` Arnd Bergmann
2008-04-11 10:41     ` Jörn Engel
2008-04-01 18:13 ` [patch 2/15] fs/logfs/logfs_abi.h joern
2008-04-08  0:24   ` Arnd Bergmann
2008-04-08  9:39     ` Jörn Engel
2008-04-08 21:52       ` Andres Salomon
2008-04-09 12:08         ` Jörn Engel
2008-04-01 18:13 ` [patch 5/15] fs/logfs/dir.c joern
2008-04-04  6:22   ` Kyungmin Park
2008-04-01 18:13 ` [patch 3/15] fs/logfs/logfs.h joern
2008-04-08  0:35   ` Arnd Bergmann
2008-04-08  9:41     ` Jörn Engel
2008-04-01 18:13 ` [patch 11/15] fs/logfs/readwrite.c joern
2008-04-01 18:13 ` [patch 13/15] fs/logfs/super.c joern
2008-04-01 18:13 ` [patch 14/15] fs/logfs/dev_bdev.c joern
2008-04-03 17:13 ` [patch 0/15] LogFS take five^Wsix Jörn Engel
2008-04-04 11:46 ` [patch 0/15] LogFS take five Jens Axboe
2008-04-07  8:22   ` Jörn Engel
2008-04-07  8:28     ` Jens Axboe
2008-04-07  9:10       ` Jörn Engel
2008-04-07  9:17         ` Jens Axboe

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=9c9fda240804032357i36e7eac0q1c639a017b27af42@mail.gmail.com \
    --to=kmpark@infradead.org \
    --cc=joern@logfs.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.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).