mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Boaz Harrosh <ooo@electrozaur.com>
To: Trond Myklebust <trondmy@primarydata.com>, hch <hch@lst.de>,
	"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
	"axboe@kernel.dk" <axboe@kernel.dk>
Cc: "linux-scsi@vger.kernel.org" <linux-scsi@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"osd-dev@open-osd.org" <osd-dev@open-osd.org>,
	"linux-block@vger.kernel.org" <linux-block@vger.kernel.org>,
	"linux-nfs@vger.kernel.org" <linux-nfs@vger.kernel.org>
Subject: Re: [PATCH 3/4] nfs: remove the objlayout driver
Date: Fri, 21 Apr 2017 16:17:41 +0300	[thread overview]
Message-ID: <272aea55-0738-5de2-ca97-414e13b478af@electrozaur.com> (raw)
In-Reply-To: <1492719505.82584.3.camel@primarydata.com>

On 04/20/2017 11:18 PM, Trond Myklebust wrote:
<>
> 
> OK. I'm applying this patch for the 4.12 merge window. 

That is understandable this code was not tested for a long while

> If, as Boaz
> suggests, there is still an interest in exofs, then I suggest we put
> that to the test by moving it into the STAGING area, to see if someone
> will step up to maintain it.
> 

I do not understand what you mean by "someone will maintain it"
What is it that is missing in exofs that you see needs development?

As I said I regularly run and test this FS and update as things advance
there where no new fixtures for a while, but no regressions either.

Please explain what it means "will maintain it"

> Cheers
>   Trond
> 

Thanks
Boaz

  parent reply	other threads:[~2017-04-21 13:17 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-12 16:01 RFC: drop the T10 OSD code and its users Christoph Hellwig
2017-04-12 16:01 ` [PATCH 1/4] block: remove the osdblk driver Christoph Hellwig
2017-04-19  7:21   ` Boaz Harrosh
2017-04-12 16:01 ` [PATCH 2/4] fs: remove exofs Christoph Hellwig
2017-04-12 16:01 ` [PATCH 3/4] nfs: remove the objlayout driver Christoph Hellwig
2017-04-20 20:18   ` Trond Myklebust
2017-04-21 10:51     ` Christoph Hellwig
2017-04-21 13:17     ` Boaz Harrosh [this message]
     [not found]       ` <B6CCD2A9-4691-45DC-AD60-E9A2ECDE22D3@primarydata.com>
2017-04-23  9:36         ` Boaz Harrosh
2017-04-21  7:27   ` Valentin Rothberg
2017-04-21 10:50     ` Christoph Hellwig
2017-04-12 16:01 ` [PATCH 4/4] scsi: remove the SCSI OSD library Christoph Hellwig
2017-04-14  2:27 ` RFC: drop the T10 OSD code and its users Martin K. Petersen
2017-04-18 16:24 ` Boaz Harrosh
2017-04-18 17:06   ` Chandy, John
2017-04-19 15:11 ` 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=272aea55-0738-5de2-ca97-414e13b478af@electrozaur.com \
    --to=ooo@electrozaur.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=martin.petersen@oracle.com \
    --cc=osd-dev@open-osd.org \
    --cc=trondmy@primarydata.com \
    /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
all inboxes | Powered by JetHome®