From: Christoph Hellwig <hch@lst.de>
To: Dave Chinner <david@fromorbit.com>
Cc: Christoph Hellwig <hch@lst.de>,
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 07:11:55 +0200 [thread overview]
Message-ID: <20160912051155.GA3972@lst.de> (raw)
In-Reply-To: <20160912015319.GC30497@dastard>
On Mon, Sep 12, 2016 at 11:53:19AM +1000, Dave Chinner wrote:
> Wasn't the lib/btree.c implementation introduced with and only used
> by logfs? Should that go as well?
The qla2xxx SCSI target driver also uses the btree library.
next prev parent reply other threads:[~2016-09-12 5:11 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
2016-09-12 5:11 ` Christoph Hellwig [this message]
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=20160912051155.GA3972@lst.de \
--to=hch@lst.de \
--cc=david@fromorbit.com \
--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).