From: linda.knippers@hpe.com (Linda Knippers)
Subject: remove long broken SCSI to NVMe translations
Date: Fri, 16 Jun 2017 09:57:16 -0400 [thread overview]
Message-ID: <5943E3BC.6050807@hpe.com> (raw)
In-Reply-To: <20170616083151.GB14698@infradead.org>
On 06/16/2017 04:31 AM, Christoph Hellwig wrote:
> [you dropped all the people in the To and Cc list..]
>
>> Someone should tell HPe, though; apparently they are using it for
>> firmware download ...
Yes, that's how we discovered it was broken.
> Everything that could be done using the scsi emulation can be trivially
> done using nvme-cli, as they should have done from day 0.
I don't quite know the history of our use of the scsi translation but I
suspect it's because we adapted some existing utility to also support nvme.
David Milburn's patch is very simple. Can we please fix the bug for now
so we have a little time to fix our tools?
Thanks,
-- ljk
>
> But adding the usual suspects to CC as they didn't seem to know it.
> And adding Robert just for fun :)
>
> _______________________________________________
> Linux-nvme mailing list
> Linux-nvme at lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-nvme
>
next prev parent reply other threads:[~2017-06-16 13:57 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
2017-06-16 6:11 ` Hannes Reinecke
2017-06-16 8:31 ` Christoph Hellwig
2017-06-16 13:57 ` Linda Knippers [this message]
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=5943E3BC.6050807@hpe.com \
--to=linda.knippers@hpe.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