Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: hch@lst.de (Christoph Hellwig)
Subject: please revert a nvme-cli commit
Date: Wed, 13 Jun 2018 09:55:57 +0200	[thread overview]
Message-ID: <20180613075557.GA22940@lst.de> (raw)

d8f949c21e9d832149518f26c71dfd8de16cd628 does bogus blind retries
on failure, and the kernel part of it was rejected.  Let's sort this
out properly.

Similarly at least for now bb2d87d7f386882005bb87fe9412af23c646c876 is
bogus as well.  We require fabrics connect to be synchronous, and changing
that will require a longer discussion first.

             reply	other threads:[~2018-06-13  7:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-13  7:55 Christoph Hellwig [this message]
2018-06-13 13:31 ` please revert a nvme-cli commit Keith Busch
2018-06-13 15:51 ` James Smart
2018-06-14 12:42   ` Christoph Hellwig
2018-06-14 16:29     ` James Smart
2018-06-15  9:38       ` Christoph Hellwig

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=20180613075557.GA22940@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox