From: hch@lst.de (Christoph Hellwig)
Subject: remove long broken SCSI to NVMe translations
Date: Wed, 14 Jun 2017 17:01:38 +0200 [thread overview]
Message-ID: <20170614150138.GA9428@lst.de> (raw)
In-Reply-To: <20170614150025.GD26073@localhost.localdomain>
On Wed, Jun 14, 2017@11:00:25AM -0400, Keith Busch wrote:
> On Wed, Jun 14, 2017@08:35:35AM +0200, Christoph Hellwig wrote:
> > TEST UNIT READY wa broken for a year and a half, and FORMAT UNIT and
> > WRITE BUFFER for two years. Instead of fixing them up remove them - no
> > one should be sending SCSI commands to non-scsi devices anyway.
>
> This is a step in the right direction, but I don't think it goes far
> enough. Can we remove the whole thing now?
I'd love to. The only real stumbling block was that some version of
SLES used it for persistent devices names. So I'd like to sync with
Hannes and Johannes to make sure they've fixed this up and upstream
kernels without the scsi translation will work just fine on SLES.
next prev parent reply other threads:[~2017-06-14 15:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 6:35 remove long broken SCSI to NVMe translations Christoph Hellwig
2017-06-14 6:35 ` [PATCH 1/2] nvme-scsi: remove TEST UNIT READY emuation Christoph Hellwig
2017-06-14 6:35 ` [PATCH 2/2] nvme-scsi: remove FORMAT UNIT and WRITE BUFFER emulations Christoph Hellwig
2017-06-14 15:00 ` remove long broken SCSI to NVMe translations Keith Busch
2017-06-14 15:01 ` Christoph Hellwig [this message]
2017-06-16 6:11 ` Hannes Reinecke
2017-06-16 8:31 ` Christoph Hellwig
2017-06-16 13:57 ` Linda Knippers
2017-06-20 6:48 ` Christoph Hellwig
2017-06-20 14:27 ` Keith Busch
2017-06-22 18:31 ` Micah Parrish
2017-06-22 19:21 ` Johannes Thumshirn
2017-06-30 13:07 ` Judy Brock
2017-06-14 15:14 ` Martin K. Petersen
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=20170614150138.GA9428@lst.de \
--to=hch@lst.de \
/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.