From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvmes fixes for Linux 5.19
Date: Thu, 30 Jun 2022 14:16:25 -0600 [thread overview]
Message-ID: <a0fd82a0-f0fa-c9ec-cd55-b6db6b60f326@kernel.dk> (raw)
In-Reply-To: <Yr39dC2Hf2/LtgXq@infradead.org>
On 6/30/22 1:45 PM, Christoph Hellwig wrote:
> The following changes since commit fbb564a557809466c171b95f8d593a0972450ff2:
>
> lib/sbitmap: Fix invalid loop in __sbitmap_queue_get_batch() (2022-06-25 10:58:55 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-5.19-2022-06-30
>
> for you to fetch changes up to e1c70d79346356bb1ede3f79436df80917845ab9:
>
> nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1 (2022-06-30 08:24:33 +0200)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 5.19
>
> - more quirks (Lamarque Vieira Souza, Pablo Greco)
> - fix a fabrics disconnect regression (Ruozhu Li)
> - fix a nvmet-tcp data_digest calculation regression (Sagi Grimberg)
> - fix nvme-tcp send failure handling (Sagi Grimberg)
> - fix a regression with nvmet-loop and passthrough controllers
> (Alan Adamson)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2022-06-30 20:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 19:45 [GIT PULL] nvmes fixes for Linux 5.19 Christoph Hellwig
2022-06-30 20:16 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-07 13:25 Christoph Hellwig
2022-07-07 23:38 ` Jens Axboe
2022-06-23 13:54 Christoph Hellwig
2022-06-23 13:55 ` Jens Axboe
2022-06-23 13:23 Christoph Hellwig
2022-06-23 13:44 ` Jens Axboe
2022-06-23 13:48 ` Christoph Hellwig
2022-06-15 13:37 Christoph Hellwig
2022-06-15 15:39 ` Jens Axboe
2022-06-02 5:28 Christoph Hellwig
2022-06-02 7:49 ` Jens Axboe
2022-06-02 7:59 ` Christoph Hellwig
2022-06-02 8:05 ` 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=a0fd82a0-f0fa-c9ec-cd55-b6db6b60f326@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=linux-block@vger.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