All of lore.kernel.org
 help / color / mirror / Atom feed
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.19-rc7
Date: Fri, 15 Jul 2022 13:50:32 -0600	[thread overview]
Message-ID: <5d50557f-e09b-acbf-690c-b82ca2d2e53d@kernel.dk> (raw)

Hi Linus,

Two NVMe fixes, and a regression fix for the core block layer from this
merge window. Please pull!


The following changes since commit 6b0de7d0f3285df849be2b3cc94fc3a0a31987bf:

  Merge tag 'nvme-5.19-2022-07-07' of git://git.infradead.org/nvme into block-5.19 (2022-07-07 17:38:19 -0600)

are available in the Git repository at:

  git://git.kernel.dk/linux-block.git tags/block-5.19-2022-07-15

for you to fetch changes up to 957a2b345cbcf41b4b25d471229f0e35262f066c:

  block: fix missing blkcg_bio_issue_init (2022-07-14 10:54:49 -0600)

----------------------------------------------------------------
block-5.19-2022-07-15

----------------------------------------------------------------
Israel Rukshin (1):
      nvme: fix block device naming collision

Jens Axboe (1):
      Merge tag 'nvme-5.19-2022-07-14' of git://git.infradead.org/nvme into block-5.19

Keith Busch (1):
      nvme-pci: fix freeze accounting for error handling

Muchun Song (1):
      block: fix missing blkcg_bio_issue_init

 block/blk-merge.c        | 1 +
 drivers/nvme/host/core.c | 6 +++---
 drivers/nvme/host/pci.c  | 9 +++++++--
 3 files changed, 11 insertions(+), 5 deletions(-)

-- 
Jens Axboe


             reply	other threads:[~2022-07-15 19:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-15 19:50 Jens Axboe [this message]
2022-07-16 18:50 ` [GIT PULL] Block fixes for 5.19-rc7 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=5d50557f-e09b-acbf-690c-b82ca2d2e53d@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.