From: Jens Axboe <axboe@kernel.dk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: "linux-block@vger.kernel.org" <linux-block@vger.kernel.org>
Subject: [GIT PULL] Block fixes for 5.8-rc4
Date: Sun, 5 Jul 2020 07:05:55 -0600 [thread overview]
Message-ID: <38cb5040-bc16-298d-bc78-624f22a9f0a1@kernel.dk> (raw)
Hi Linus,
A few later fixes came in after the initial -rc4 pull request, let's
flush them out before the release is tagged.
- NVMe pull request from Christoph
- Fix crash in multi-path disk add (Christoph)
- Fix ignore of identify error (Sagi)
- Fix a compiler complaint that a function should be static (Wei)
Please pull!
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.kernel.dk/linux-block.git tags/block-5.8-2020-07-05
for you to fetch changes up to 3197d48a7c04eee3e50bd54ef7e17e383b8a919e:
block: make function __bio_integrity_free() static (2020-07-02 12:38:18 -0600)
----------------------------------------------------------------
block-5.8-2020-07-05
----------------------------------------------------------------
Christoph Hellwig (1):
nvme: fix a crash in nvme_mpath_add_disk
Jens Axboe (1):
Merge branch 'nvme-5.8' of git://git.infradead.org/nvme into block-5.8
Sagi Grimberg (1):
nvme: fix identify error status silent ignore
Wei Yongjun (1):
block: make function __bio_integrity_free() static
block/bio-integrity.c | 3 ++-
drivers/nvme/host/core.c | 12 +++++++++---
drivers/nvme/host/multipath.c | 7 ++++---
3 files changed, 15 insertions(+), 7 deletions(-)
--
Jens Axboe
next reply other threads:[~2020-07-05 13:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-05 13:05 Jens Axboe [this message]
2020-07-05 18:00 ` [GIT PULL] Block fixes for 5.8-rc4 pr-tracker-bot
-- strict thread matches above, loose matches on Subject: below --
2020-07-02 4:31 Jens Axboe
2020-07-02 22:30 ` pr-tracker-bot
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=38cb5040-bc16-298d-bc78-624f22a9f0a1@kernel.dk \
--to=axboe@kernel.dk \
--cc=linux-block@vger.kernel.org \
--cc=torvalds@linux-foundation.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 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.