From: Christoph Hellwig <hch@lst.de>
To: ooo@electrozaur.com, martin.petersen@oracle.com
Cc: Nick Desaulniers <ndesaulniers@google.com>,
Nathan Chancellor <natechancellor@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
osd-dev@open-osd.org, linux-scsi@vger.kernel.org,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: remove exofs and the T10 OSD code V2
Date: Sat, 27 Oct 2018 10:20:17 +0200 [thread overview]
Message-ID: <20181027082019.20838-1-hch@lst.de> (raw)
The only real user of the T10 OSD protocol, the pNFS object layout
driver never went to the point of having shipping products, and we
removed it 1.5 years ago. Exofs is just a simple example without
real life users.
The code has been mostly unmaintained for years and is getting in the
way of block / SCSI changes, so I think it's finally time to drop it.
Quote from Boaz:
"As I said then. It is used in Universities for studies and experiments.
Every once in a while. I get an email with questions and reports.
But yes feel free to remove the all thing!!
I guess I can put it up on github. In a public tree.
Just that I will need to forward port it myself, til now you guys
been doing this for me ;-)"
next reply other threads:[~2018-10-27 8:20 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 8:20 Christoph Hellwig [this message]
2018-10-27 8:20 ` [PATCH 1/2] fs: remove exofs Christoph Hellwig
2018-10-29 20:41 ` Bart Van Assche
2018-10-27 8:20 ` [PATCH 2/2] scsi: remove the SCSI OSD library Christoph Hellwig
2018-10-29 20:43 ` Bart Van Assche
2018-10-27 20:32 ` remove exofs and the T10 OSD code V2 Nick Desaulniers
2018-10-29 20:42 ` Jens Axboe
2018-10-30 7:45 ` Christoph Hellwig
2018-10-31 15:57 ` Boaz Harrosh
2018-10-31 21:10 ` Douglas Gilbert
2018-11-01 0:03 ` Boaz Harrosh
2018-11-01 11:13 ` Douglas Gilbert
2018-10-31 15:59 ` Jens Axboe
2018-10-31 16:34 ` Boaz Harrosh
2018-10-31 17:29 ` Bart Van Assche
2018-10-31 17:47 ` Boaz Harrosh
2018-10-31 22:07 ` Finn Thain
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=20181027082019.20838-1-hch@lst.de \
--to=hch@lst.de \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=natechancellor@gmail.com \
--cc=ndesaulniers@google.com \
--cc=ooo@electrozaur.com \
--cc=osd-dev@open-osd.org \
--cc=torvalds@linux-foundation.org \
/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).