From: Dave Chinner <david@fromorbit.com>
To: Christoph Hellwig <hch@lst.de>
Cc: viro@zeniv.linux.org.uk, joern@logfs.org,
prasadjoshi.linux@gmail.com, logfs@logfs.org,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] logfs: remove from tree
Date: Mon, 12 Sep 2016 11:53:19 +1000 [thread overview]
Message-ID: <20160912015319.GC30497@dastard> (raw)
In-Reply-To: <1473599062-23550-1-git-send-email-hch@lst.de>
On Sun, Sep 11, 2016 at 03:04:22PM +0200, Christoph Hellwig wrote:
> Logfs was introduced to the kernel in 2009, and hasn't seen any non
> drive-by changes since 2012, while having lots of unsolved issues
> including the complete lack of error handling, with more and more
> issues popping up without any fixes.
>
> The logfs.org domain has been bouncing from a mail, and the maintainer
> on the non-logfs.org domain hasn't repsonded to past queries either.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
> ---
> Documentation/filesystems/00-INDEX | 2 -
> Documentation/filesystems/logfs.txt | 241 ----
> MAINTAINERS | 8 -
> fs/Kconfig | 1 -
> fs/Makefile | 1 -
> fs/logfs/Kconfig | 17 -
> fs/logfs/Makefile | 13 -
> fs/logfs/compr.c | 95 --
> fs/logfs/dev_bdev.c | 322 -----
> fs/logfs/dev_mtd.c | 274 -----
> fs/logfs/dir.c | 797 ------------
> fs/logfs/file.c | 285 -----
> fs/logfs/gc.c | 732 -----------
> fs/logfs/inode.c | 428 -------
> fs/logfs/journal.c | 894 --------------
> fs/logfs/logfs.h | 735 -----------
> fs/logfs/logfs_abi.h | 629 ----------
> fs/logfs/readwrite.c | 2298 -----------------------------------
> fs/logfs/segment.c | 961 ---------------
> fs/logfs/super.c | 653 ----------
Wasn't the lib/btree.c implementation introduced with and only used
by logfs? Should that go as well?
Cheers,
Dave.
--
Dave Chinner
david@fromorbit.com
next prev parent reply other threads:[~2016-09-12 1:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-11 13:04 [PATCH] logfs: remove from tree Christoph Hellwig
2016-09-12 1:53 ` Dave Chinner [this message]
2016-09-12 5:11 ` Christoph Hellwig
2016-09-12 6:55 ` Artem Bityutskiy
2016-09-12 15:53 ` Austin S. Hemmelgarn
2016-10-15 0:33 ` Al Viro
2016-10-24 6:37 ` Christoph Hellwig
2016-12-01 10:06 ` Christoph Hellwig
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=20160912015319.GC30497@dastard \
--to=david@fromorbit.com \
--cc=hch@lst.de \
--cc=joern@logfs.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=logfs@logfs.org \
--cc=prasadjoshi.linux@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).