public inbox for linux-block@vger.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 6.1-rc8/final
Date: Fri, 2 Dec 2022 14:38:06 -0700	[thread overview]
Message-ID: <0429607c-d5b1-6d6f-2cff-7b35f02a562d@kernel.dk> (raw)

Hi Linus,

Just a small NVMe merge for this week, fixing protection of the name
space list, and a missing clear of a reserved field when unused.

Please pull!


The following changes since commit 7d4a93176e0142ce16d23c849a47d5b00b856296:

  ublk_drv: don't forward io commands in reserve order (2022-11-23 20:36:57 -0700)

are available in the Git repository at:

  git://git.kernel.dk/linux.git tags/block-6.1-2022-12-02

for you to fetch changes up to d0f411c0b9bdef85f647e15a2fcc790b29891f2c:

  Merge tag 'nvme-6.1-2022-01-02' of git://git.infradead.org/nvme into block-6.1 (2022-12-02 08:01:06 -0700)

----------------------------------------------------------------
block-6.1-2022-12-02

----------------------------------------------------------------
Caleb Sander (1):
      nvme: fix SRCU protection of nvme_ns_head list

Jens Axboe (1):
      Merge tag 'nvme-6.1-2022-01-02' of git://git.infradead.org/nvme into block-6.1

Lei Rao (1):
      nvme-pci: clear the prp2 field when not used

 drivers/nvme/host/core.c      | 2 +-
 drivers/nvme/host/multipath.c | 3 +++
 drivers/nvme/host/pci.c       | 2 ++
 3 files changed, 6 insertions(+), 1 deletion(-)

-- 
Jens Axboe

             reply	other threads:[~2022-12-02 21:38 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 21:38 Jens Axboe [this message]
2022-12-03  0:30 ` [GIT PULL] Block fixes for 6.1-rc8/final 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=0429607c-d5b1-6d6f-2cff-7b35f02a562d@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox