linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Keith Busch <kbusch@kernel.org>
To: Jens Axboe <axboe@kernel.dk>
Cc: linux-nvme@lists.infradead.org, hch@lst.de,
	Chaitanya.Kulkarni@wdc.com, sagi@grimberg.me
Subject: [GIT PULL] nvme for 5.6-rc
Date: Sat, 15 Feb 2020 02:09:39 +0900	[thread overview]
Message-ID: <20200214170939.GB10757@redsun51.ssa.fujisawa.hgst.com> (raw)

The following changes since commit bb6d3fb354c5ee8d6bde2d576eb7220ea09862b9:

  Linux 5.6-rc1 (2020-02-09 16:08:48 -0800)

are available in the Git repository at:

  git://git.infradead.org/nvme.git nvme-5.6-rc

for you to fetch changes up to 4c8337a0b7bb7fe7ffd75a7be2aa40804442cf16:

  nvme: fix the parameter order for nvme_get_log in nvme_get_fw_slot_info (2020-02-14 23:24:23 +0900)

----------------------------------------------------------------
Anton Eidelman (1):
      nvme/tcp: fix bug on double requeue when send fails

Keith Busch (1):
      nvme/pci: move cqe check after device shutdown

Nigel Kirkland (1):
      nvme: prevent warning triggered by nvme_stop_keep_alive

Yi Zhang (1):
      nvme: fix the parameter order for nvme_get_log in nvme_get_fw_slot_info

 drivers/nvme/host/core.c | 12 ++++++------
 drivers/nvme/host/pci.c  | 23 ++++++++++++++++++-----
 drivers/nvme/host/rdma.c |  2 +-
 drivers/nvme/host/tcp.c  |  9 +++++++--
 4 files changed, 32 insertions(+), 14 deletions(-)


_______________________________________________
linux-nvme mailing list
linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme

             reply	other threads:[~2020-02-14 17:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 17:09 Keith Busch [this message]
2020-02-14 17:12 ` [GIT PULL] nvme for 5.6-rc 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=20200214170939.GB10757@redsun51.ssa.fujisawa.hgst.com \
    --to=kbusch@kernel.org \
    --cc=Chaitanya.Kulkarni@wdc.com \
    --cc=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    /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;
as well as URLs for NNTP newsgroup(s).