public inbox for linux-nvme@lists.infradead.org
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, hch@lst.de
Subject: Re: [GIT PULL REDO] nvme fixes for Linux 6.6
Date: Wed, 18 Oct 2023 15:34:57 -0600	[thread overview]
Message-ID: <da26d8c0-46b5-4a0d-8c8f-e924cec88e6b@kernel.dk> (raw)
In-Reply-To: <ZTBLFYbo8iuhF9kZ@kbusch-mbp>

On 10/18/23 3:16 PM, Keith Busch wrote:
> The previous contained a patch that needs additional consideration. This
> pull request is the same as before, minus the non-root passthrough
> revert.
> 
> The following changes since commit 07a1141ff170ff5d4f9c4fbb0453727ab48096e5:
> 
>   nbd: don't call blk_mark_disk_dead nbd_clear_sock_ioctl (2023-10-03 18:27:44 -0600)
> 
> are available in the Git repository at:
> 
>   git://git.infradead.org/nvme.git tags/nvme-6.6-2023-10-18
> 
> for you to fetch changes up to 5c3f4066462a5f6cac04d3dd81c9f551fabbc6c7:
> 
>   nvme-pci: add BOGUS_NID for Intel 0a54 device (2023-10-18 14:08:39 -0700)
> 
> ----------------------------------------------------------------
> nvme fixes for Linux 6.6
> 
>  - nvme-rdma queue fix (Maurizio)
>  - nvmet-auth double free fix (Maurizio)
>  - nvme-tcp use-after-free fix (Sagi)
>  - nvme-auth data direction fix (Martin)
>  - nvme passthrough metadata sanitization (Keith)
>  - nvme bogus identifiers for multi-controller ssd (Keith)

Pulled, thanks.

-- 
Jens Axboe



      reply	other threads:[~2023-10-18 21:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-18 21:16 [GIT PULL REDO] nvme fixes for Linux 6.6 Keith Busch
2023-10-18 21:34 ` Jens Axboe [this message]

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=da26d8c0-46b5-4a0d-8c8f-e924cec88e6b@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=hch@lst.de \
    --cc=kbusch@kernel.org \
    --cc=linux-nvme@lists.infradead.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