Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [PATCH] nvme/pci: Poll CQ on timeout
Date: Thu, 20 Apr 2017 12:28:55 -0400	[thread overview]
Message-ID: <20170420162855.GA25259@localhost.localdomain> (raw)
In-Reply-To: <8ae3cdeb-0c81-7ce9-758e-717d7955808c@grimberg.me>

On Thu, Apr 20, 2017@07:17:40PM +0300, Sagi Grimberg wrote:
> 
> > > Thanks, I forgot about this one, but still think it's a good idea.
> > > Applied it to for-next.
> > 
> > Agree, it's a nice addition.
> 
> I think its harmless to have. especially when we do log that it
> happened.

It's actually proved to be quite useful and maybe good for stable. Any
objections to roll this into 4.11 instead 4.12?

  reply	other threads:[~2017-04-20 16:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24 22:59 [PATCH] nvme/pci: Poll CQ on timeout Keith Busch
2017-02-27 14:42 ` Sagi Grimberg
2017-02-28 14:10 ` Christoph Hellwig
2017-02-28 16:00   ` Keith Busch
2017-02-28 17:44     ` Jens Axboe
2017-04-20  8:56       ` Johannes Thumshirn
2017-04-20 14:20         ` Keith Busch
2017-04-20 15:45           ` Jens Axboe
2017-04-20 16:17             ` Sagi Grimberg
2017-04-20 16:28               ` Keith Busch [this message]
2017-04-20 16:31                 ` Jens Axboe
2017-04-21  6:39                   ` 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=20170420162855.GA25259@localhost.localdomain \
    --to=keith.busch@intel.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