All of lore.kernel.org
 help / color / mirror / Atom feed
From: keith.busch@intel.com (Keith Busch)
Subject: [GIT PULL] nvme fix for 4.16-rc6
Date: Fri, 16 Mar 2018 10:01:10 -0600	[thread overview]
Message-ID: <20180316160110.GC720@localhost.localdomain> (raw)

Hi Jens,

One last fix from Jianchao to address a troubling scenario Ming identified
with offlining CPUs that could leave nvme controllers unusable. We can
not allow that to occur, so we wish to include a new IRQ spread that
prevents that situation.

The following changes since commit 0c8efd610b58cb23cefdfa12015799079aef94ae:

  Linux 4.16-rc5 (2018-03-11 17:25:09 -0700)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-4.16-rc6

for you to fetch changes up to 3aadd3b10f018f26c451f8a0feac7605c2deb0c7:

  nvme-pci: assign separate irq vectors for adminq and ioq1 (2018-03-13 11:27:57 -0600)

----------------------------------------------------------------
Jianchao Wang (1):
      nvme-pci: assign separate irq vectors for adminq and ioq1

 drivers/nvme/host/pci.c | 29 ++++++++++++++++++++++-------
 1 file changed, 22 insertions(+), 7 deletions(-)

             reply	other threads:[~2018-03-16 16:01 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-16 16:01 Keith Busch [this message]
2018-03-16 16:14 ` [GIT PULL] nvme fix for 4.16-rc6 Jens Axboe
2018-03-16 16:16   ` Christoph Hellwig
2018-03-16 16:26     ` Jens Axboe
2018-03-16 16:53       ` Keith Busch
2018-03-21 20:59       ` Keith Busch
2018-03-21 21:02         ` Jens Axboe
2018-03-21 21:44           ` Jens Axboe
2018-03-21 22:08             ` Keith Busch
2018-03-22 21:09             ` Keith Busch
2018-03-22 21:32               ` Jens Axboe
2018-03-22 22:02                 ` Keith Busch
2018-03-22 22:09                   ` Jens Axboe

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=20180316160110.GC720@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 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.