From: Bart Van Assche <bvanassche@acm.org>
To: Christoph Hellwig <hch@lst.de>,
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: Re: [PATCH 1/2] fs: remove exofs
Date: Mon, 29 Oct 2018 13:41:33 -0700 [thread overview]
Message-ID: <1540845693.196084.96.camel@acm.org> (raw)
In-Reply-To: <20181027082019.20838-2-hch@lst.de>
On Sat, 2018-10-27 at 10:20 +0200, Christoph Hellwig wrote:
> This was an example for using the SCSI OSD protocol, which we're trying
> to remove.
Reviewed-by: Bart Van Assche <bvanassche@acm.org>
next prev parent reply other threads:[~2018-10-30 5:31 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 8:20 remove exofs and the T10 OSD code V2 Christoph Hellwig
2018-10-27 8:20 ` [PATCH 1/2] fs: remove exofs Christoph Hellwig
2018-10-29 20:41 ` Bart Van Assche [this message]
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-30 7:45 ` Christoph Hellwig
2018-10-31 15:57 ` Boaz Harrosh
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=1540845693.196084.96.camel@acm.org \
--to=bvanassche@acm.org \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.