From: Christoph Hellwig <hch@infradead.org>
To: Jens Axboe <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 fix for 5.8
Date: Thu, 16 Jul 2020 16:42:05 +0200 [thread overview]
Message-ID: <20200716144205.GA475287@infradead.org> (raw)
The following changes since commit 579dd91ab3a5446b148e7f179b6596b270dace46:
nbd: Fix memory leak in nbd_add_socket (2020-07-08 15:42:18 -0600)
are available in the Git repository at:
git://git.infradead.org/nvme.git nvme-5.8
for you to fetch changes up to 05b29021fba5e725dd385151ef00b6340229b500:
nvme: explicitly update mpath disk capacity on revalidation (2020-07-16 16:40:27 +0200)
----------------------------------------------------------------
Anthony Iliopoulos (1):
nvme: explicitly update mpath disk capacity on revalidation
drivers/nvme/host/core.c | 1 +
drivers/nvme/host/nvme.h | 13 +++++++++++++
2 files changed, 14 insertions(+)
next reply other threads:[~2020-07-16 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 14:42 Christoph Hellwig [this message]
2020-07-16 14:58 ` [GIT PULL] nvme fix for 5.8 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=20200716144205.GA475287@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox