From: Jens Axboe <axboe@kernel.dk>
To: Keith Busch <kbusch@kernel.org>
Cc: linux-nvme@lists.infradead.org, hch@lst.de, sagi@grimberg.me
Subject: Re: [GIT PULL] nvme fixes for Linux 6.5
Date: Thu, 13 Jul 2023 14:31:42 -0600 [thread overview]
Message-ID: <e1df21c6-1bf5-ab8c-d66c-7d55eb6df9c9@kernel.dk> (raw)
In-Reply-To: <ZLBdlPjrbvdex1Hq@kbusch-mbp.dhcp.thefacebook.com>
On 7/13/23 2:24 PM, Keith Busch wrote:
> The following changes since commit 2fb48d88e77f29bf9d278f25bcfe82cf59a0e09b:
>
> blk-crypto: use dynamic lock class for blk_crypto_profile::lock (2023-07-05 16:36:12 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.5-2023-07-13
>
> for you to fetch changes up to b8f6446b6853768cb99e7c201bddce69ca60c15e:
>
> nvme-pci: fix DMA direction of unmapping integrity data (2023-07-13 08:16:07 -0700)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.5
>
> - Don't require quirk to use duplicate namespace identifiers
> (Christoph, Sagi)
> - One more BOGUS_NID quirk (Pankaj)
> - IO timeout and error hanlding fixes for PCI (Keith)
> - Enhanced metadata format mask fix (Ankit)
> - Association race condition fix for fibre channel (Michael)
> - Correct debugfs error checks (Minjie)
> - Use PAGE_SECTORS_SHIFT where needed (Damien)
> - Reduce kernel logs for legacy nguid attribute (Keith)
> - Use correct dma direction when unmapping metadata (Ming)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2023-07-13 20:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-13 20:24 [GIT PULL] nvme fixes for Linux 6.5 Keith Busch
2023-07-13 20:31 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-08-03 14:52 Keith Busch
2023-08-04 2:04 ` 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=e1df21c6-1bf5-ab8c-d66c-7d55eb6df9c9@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kbusch@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;
as well as URLs for NNTP newsgroup(s).