From: Christoph Hellwig <hch@infradead.org>
To: Boaz Harrosh <boaz@plexistor.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
Alexander Viro <viro@zeniv.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Please add the zuf tree to linux-next
Date: Wed, 23 Oct 2019 19:36:06 -0700 [thread overview]
Message-ID: <20191024023606.GA1884@infradead.org> (raw)
In-Reply-To: <1b192a85-e1da-0925-ef26-178b93d0aa45@plexistor.com>
On Thu, Oct 24, 2019 at 03:34:29AM +0300, Boaz Harrosh wrote:
> Hello Stephen
>
> Please add the zuf tree below to the linux-next tree.
> [https://github.com/NetApp/zufs-zuf zuf]
I don't remember us coming to the conclusion that this actually is
useful doesn't just badly duplicate the fuse functionality.
next prev parent reply other threads:[~2019-10-24 2:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-24 0:34 Please add the zuf tree to linux-next Boaz Harrosh
2019-10-24 2:36 ` Christoph Hellwig [this message]
2019-10-29 5:07 ` Stephen Rothwell
2019-10-29 5:53 ` Christoph Hellwig
2019-11-14 14:02 ` Boaz Harrosh
2019-11-14 14:56 ` Miklos Szeredi
2019-11-14 16:04 ` Boaz Harrosh
2019-11-15 8:04 ` Miklos Szeredi
2019-11-18 15:44 ` Boaz Harrosh
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=20191024023606.GA1884@infradead.org \
--to=hch@infradead.org \
--cc=boaz@plexistor.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sfr@canb.auug.org.au \
--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).