linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Alexander Belyakov" <abelyako@googlemail.com>
To: "Jörn Engel" <joern@lazybastard.org>
Cc: linux-mtd@lists.infradead.org
Subject: Re: LogFS take four
Date: Wed, 6 Jun 2007 17:50:44 +0400	[thread overview]
Message-ID: <fe810cf0706060650p48df811dw9f1dd90b2b9f145d@mail.gmail.com> (raw)
In-Reply-To: <20070603183845.GA8952@lazybastard.org>

On 6/3/07, Jörn Engel <joern@lazybastard.org> wrote:
> This round the patch is split into file-sized hunks.  There actually
> seem to be kernel developers not manly enough to digest 6000+ lines of
> code at once.  An I thought I was the only wimp around.
>
> [...]

Small question about compr.c. Sorry not posting in proper thread -
just have no original message to reply to.

Why do you use __exit macros with logfs_compr_exit()? You will get an
build-time error if logfs is compiled as part of the kernel (not
module) just because logfs_init() calls logfs_compr_exit().

Thanks,
Alexander

  parent reply	other threads:[~2007-06-06 13:50 UTC|newest]

Thread overview: 65+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-03 18:38 LogFS take four Jörn Engel
2007-06-03 18:49 ` [Patch 02/18] fs/Makefile Jörn Engel
2007-06-03 18:49 ` [Patch 01/18] fs/Kconfig Jörn Engel
2007-06-03 19:00 ` [Patch 16/18] fs/logfs/progs/fsck.c Jörn Engel
2007-06-03 19:01 ` [Patch 17/18] fs/logfs/progs/mkfs.c Jörn Engel
2007-06-03 19:20 ` LogFS take four Jan-Benedict Glaw
2007-06-03 19:19   ` Jörn Engel
2007-06-03 19:43 ` [Patch 07/18] fs/logfs/dir.c Jörn Engel
2007-06-15  8:59   ` Evgeniy Polyakov
2007-06-15 11:57     ` Jörn Engel
2007-06-03 20:00 ` [Patch 11/18] fs/logfs/journal.c Jörn Engel
2007-06-03 20:01 ` [Patch 05/18] fs/logfs/logfs.h Jörn Engel
2007-06-03 21:50   ` Arnd Bergmann
2007-06-04  8:17     ` Jan Engelhardt
2007-06-04  9:11     ` Jörn Engel
2007-06-06 11:29   ` Paulo Marques
2007-06-06 11:29     ` Jörn Engel
2007-06-03 20:14 ` [Patch 06/18] fs/logfs/compr.c Jörn Engel
2007-06-03 21:58   ` Arnd Bergmann
2007-06-04  8:54     ` Jörn Engel
2007-06-04 13:53       ` David Woodhouse
2007-06-03 20:14 ` [Patch 14/18] fs/logfs/segment.c Jörn Engel
2007-06-03 22:21   ` Arnd Bergmann
2007-06-04  9:07     ` Jörn Engel
2007-06-03 20:21 ` [Patch 03/18] fs/logfs/Makefile Jörn Engel
2007-06-03 20:30 ` [Patch 08/18] fs/logfs/file.c Jörn Engel
2007-06-03 20:42 ` [Patch 15/18] fs/logfs/super.c Jörn Engel
2007-06-10 16:27   ` Arnd Bergmann
2007-06-10 17:38     ` Jörn Engel
2007-06-10 18:33       ` Arnd Bergmann
2007-06-10 19:10         ` Jörn Engel
2007-06-10 19:20           ` Willy Tarreau
2007-06-03 20:43 ` [Patch 12/18] fs/logfs/memtree.c Jörn Engel
2007-06-03 20:46 ` [Patch 09/18] fs/logfs/gc.c Jörn Engel
2007-06-03 22:07   ` Arnd Bergmann
2007-06-04  9:01     ` Jörn Engel
2007-06-15  9:03   ` Evgeniy Polyakov
2007-06-15 11:14     ` Jörn Engel
2007-06-15 13:03       ` Evgeniy Polyakov
2007-06-03 20:57 ` [Patch 13/18] fs/logfs/readwrite.c Jörn Engel
2007-06-03 21:21 ` [Patch 18/18] fs/logfs/Locking Jörn Engel
2007-06-03 21:27 ` [Patch 10/18] fs/logfs/inode.c Jörn Engel
2007-06-10 17:24   ` Arnd Bergmann
2007-06-10 17:40     ` Jörn Engel
2007-06-11 23:28     ` Jörn Engel
2007-06-11 23:51       ` Arnd Bergmann
2007-06-11 23:57         ` Jörn Engel
2007-06-03 21:58 ` [Patch 04/18] include/linux/logfs.h Jörn Engel
2007-06-03 21:42   ` Arnd Bergmann
2007-06-04  9:12     ` Jörn Engel
2007-06-04 13:38       ` David Woodhouse
2007-06-04 14:02         ` Jörn Engel
2007-06-05 15:49         ` Segher Boessenkool
2007-06-05 15:53           ` David Woodhouse
2007-06-05 18:49             ` Segher Boessenkool
2007-06-06  8:50               ` David Woodhouse
2007-06-06  8:59                 ` Andreas Schwab
2007-06-06 12:42                 ` Arnd Bergmann
2007-06-05 20:39           ` Bill Davidsen
2007-06-03 22:18 ` LogFS take four Arnd Bergmann
2007-06-04  9:05   ` Jörn Engel
2007-06-06 13:50 ` Alexander Belyakov [this message]
2007-06-06 13:58   ` Jörn Engel
2007-06-15  8:37 ` Evgeniy Polyakov
2007-06-15 11:10   ` Jörn Engel

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=fe810cf0706060650p48df811dw9f1dd90b2b9f145d@mail.gmail.com \
    --to=abelyako@googlemail.com \
    --cc=joern@lazybastard.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).