From: Christoph Hellwig <hch@infradead.org>
To: axboe@kernel.dk
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for 5.8
Date: Thu, 2 Jul 2020 10:42:07 +0200 [thread overview]
Message-ID: <20200702084207.GA3718469@infradead.org> (raw)
The following changes since commit e7eea44eefbdd5f0345a0a8b80a3ca1c21030d06:
virtio-blk: free vblk-vqs in error path of virtblk_probe() (2020-06-30 19:02:58 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.8
for you to fetch changes up to 72d447113bb751ded97b2e2c38f886e4a4139082:
nvme: fix a crash in nvme_mpath_add_disk (2020-07-02 10:38:00 +0200)
----------------------------------------------------------------
Christoph Hellwig (1):
nvme: fix a crash in nvme_mpath_add_disk
Sagi Grimberg (1):
nvme: fix identify error status silent ignore
drivers/nvme/host/core.c | 12 +++++++++---
drivers/nvme/host/multipath.c | 7 ++++---
2 files changed, 13 insertions(+), 6 deletions(-)
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: axboe@kernel.dk
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: [GIT PULL] nvme fixes for 5.8
Date: Thu, 2 Jul 2020 10:42:07 +0200 [thread overview]
Message-ID: <20200702084207.GA3718469@infradead.org> (raw)
The following changes since commit e7eea44eefbdd5f0345a0a8b80a3ca1c21030d06:
virtio-blk: free vblk-vqs in error path of virtblk_probe() (2020-06-30 19:02:58 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.8
for you to fetch changes up to 72d447113bb751ded97b2e2c38f886e4a4139082:
nvme: fix a crash in nvme_mpath_add_disk (2020-07-02 10:38:00 +0200)
----------------------------------------------------------------
Christoph Hellwig (1):
nvme: fix a crash in nvme_mpath_add_disk
Sagi Grimberg (1):
nvme: fix identify error status silent ignore
drivers/nvme/host/core.c | 12 +++++++++---
drivers/nvme/host/multipath.c | 7 ++++---
2 files changed, 13 insertions(+), 6 deletions(-)
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
next reply other threads:[~2020-07-02 8:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-02 8:42 Christoph Hellwig [this message]
2020-07-02 8:42 ` [GIT PULL] nvme fixes for 5.8 Christoph Hellwig
2020-07-02 18:11 ` Jens Axboe
2020-07-02 18:11 ` Jens Axboe
-- strict thread matches above, loose matches on Subject: below --
2020-07-29 17:30 Christoph Hellwig
2020-07-29 17:30 ` Christoph Hellwig
2020-07-29 17:37 ` Jens Axboe
2020-07-29 17:37 ` Jens Axboe
2020-07-29 17:09 Christoph Hellwig
2020-07-29 17:09 ` Christoph Hellwig
2020-07-29 17:22 ` Jens Axboe
2020-07-29 17:22 ` Jens Axboe
2020-07-29 17:29 ` Christoph Hellwig
2020-07-29 17:29 ` Christoph Hellwig
2020-06-25 16:53 Christoph Hellwig
2020-06-25 16:53 ` Christoph Hellwig
2020-06-25 18:57 ` Jens Axboe
2020-06-25 18:57 ` Jens Axboe
2020-06-11 6:22 Christoph Hellwig
2020-06-11 6:22 ` Christoph Hellwig
2020-06-11 15:10 ` Jens Axboe
2020-06-11 15:10 ` 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=20200702084207.GA3718469@infradead.org \
--to=hch@infradead.org \
--cc=axboe@kernel.dk \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.kernel.org \
--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 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.