From: hch@infradead.org (Christoph Hellwig)
Subject: [GIT PULL] nvme fixes for 5.1
Date: Thu, 28 Mar 2019 18:19:28 +0100 [thread overview]
Message-ID: <20190328171928.GA26641@infradead.org> (raw)
A few accumulated small fixes:
- fix an endianess misannotation that sneaked in this merge window in
nvme-tcp (me)
- fix nvme-loop to handle multi-page segments (Ming)
- fix error handling in the nvmet configfs code (Max)
- add a missing requeue point in the multipath code (Martin George)
The following changes since commit dd08a8d9a66de4b54575c294a92630299f7e0fe7:
libata: fix using DMA buffers on stack (2019-03-28 08:16:04 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.1
for you to fetch changes up to a536b49785759bf99465fdf6e248d34322123fcd:
nvmet: fix error flow during ns enable (2019-03-28 18:15:03 +0100)
----------------------------------------------------------------
Christoph Hellwig (1):
nvme-tcp: fix an endianess miss-annotation
Martin George (1):
nvme-multipath: relax ANA state check
Max Gurtovoy (1):
nvmet: fix error flow during ns enable
Ming Lei (1):
nvmet: fix building bvec from sg list
drivers/nvme/host/multipath.c | 5 +----
drivers/nvme/host/tcp.c | 2 +-
drivers/nvme/target/core.c | 4 ++--
drivers/nvme/target/io-cmd-file.c | 20 ++++++++++----------
4 files changed, 14 insertions(+), 17 deletions(-)
next reply other threads:[~2019-03-28 17:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-28 17:19 Christoph Hellwig [this message]
2019-03-28 17:22 ` [GIT PULL] nvme fixes for 5.1 Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2019-04-11 15:31 Christoph Hellwig
2019-04-11 15:37 ` 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=20190328171928.GA26641@infradead.org \
--to=hch@infradead.org \
/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