From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>, Sagi Grimberg <sagi@grimberg.me>,
Chaitanya Kulkarni <kch@nvidia.com>,
linux-block@vger.kernel.org, linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] nvme fix for Linux 6.3
Date: Wed, 1 Mar 2023 07:50:46 -0700 [thread overview]
Message-ID: <65c8524f-e21c-04e4-c56f-8bb24eca9cb0@kernel.dk> (raw)
In-Reply-To: <Y/9Xn595ioya85dO@infradead.org>
On 3/1/23 6:48 AM, Christoph Hellwig wrote:
> The following changes since commit 310726c33ad76cebdee312dbfafc12c1b44bf977:
>
> block: be a bit more careful in checking for NULL bdev while polling (2023-02-24 13:19:59 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.3-2022-03-01
>
> for you to fetch changes up to 26a57cb35548ae67c14871cccbf50da3edb01ea4:
>
> nvme-fabrics: show well known discovery name (2023-02-28 06:14:44 -0700)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.3
>
> - don't access released socket during error recovery (Akinobu Mita)
> - bring back auto-removal of deleted namespaces during sequential scan
> (Christoph Hellwig)
> - fix an error code in nvme_auth_process_dhchap_challenge
> (Dan Carpenter)
> - show well known discovery name (Daniel Wagner)
> - add a missing endianess conversion in effects masking (Keith Busch)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2023-03-01 14:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 13:48 [GIT PULL] nvme fix for Linux 6.3 Christoph Hellwig
2023-03-01 14:50 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-06 13:56 Christoph Hellwig
2023-04-06 14:12 ` Jens Axboe
2023-04-14 5:16 Christoph Hellwig
2023-04-14 12:29 ` 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=65c8524f-e21c-04e4-c56f-8bb24eca9cb0@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--cc=kch@nvidia.com \
--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