From: Christoph Hellwig <hch@infradead.org>
To: Trond Myklebust <trondmy@primarydata.com>
Cc: hch <hch@lst.de>, "ooo@electrozaur.com" <ooo@electrozaur.com>,
"martin.petersen@oracle.com" <martin.petersen@oracle.com>,
"axboe@kernel.dk" <axboe@kernel.dk>,
"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 03:51:16 -0700 [thread overview]
Message-ID: <20170421105116.GB28396@infradead.org> (raw)
In-Reply-To: <1492719505.82584.3.camel@primarydata.com>
On Thu, Apr 20, 2017 at 08:18:28PM +0000, Trond Myklebust wrote:
> OK. I'm applying this patch for the 4.12 merge window. 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 think that would be a good idea, I'll can prepare a patch for the
net merge window.
next prev parent reply other threads:[~2017-04-21 10:51 UTC|newest]
Thread overview: 14+ 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 3/4] nfs: remove the objlayout driver Christoph Hellwig
2017-04-20 20:18 ` Trond Myklebust
2017-04-21 10:51 ` Christoph Hellwig [this message]
2017-04-21 13:17 ` Boaz Harrosh
[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-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=20170421105116.GB28396@infradead.org \
--to=hch@infradead.org \
--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=ooo@electrozaur.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;
as well as URLs for NNTP newsgroup(s).