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 fixes for Linux 6.2
Date: Thu, 26 Jan 2023 11:44:17 -0700 [thread overview]
Message-ID: <6bea4ea1-9dac-6d74-c3b8-54982fd3de66@kernel.dk> (raw)
In-Reply-To: <Y9K6fTTrhXSWkVeZ@infradead.org>
On 1/26/23 10:38 AM, Christoph Hellwig wrote:
> The following changes since commit 955bc12299b17aa60325e1748336e1fd1e664ed0:
>
> Merge tag 'nvme-6.2-2023-01-20' of git://git.infradead.org/nvme into block-6.2 (2023-01-20 08:08:29 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.2-2023-01-26
>
> for you to fetch changes up to 85eee6341abb81ac6a35062ffd5c3029eb53be6b:
>
> nvme: fix passthrough csi check (2023-01-25 07:09:38 +0100)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.2
>
> - flush initial scan_work for async probe (Keith Busch)
> - fix passthrough csi check (Keith Busch)
> - fix nvme-fc initialization order (Ross Lagerwall)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2023-01-26 18:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-26 17:38 [GIT PULL] nvme fixes for Linux 6.2 Christoph Hellwig
2023-01-26 18:44 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-15 18:14 Christoph Hellwig
2023-02-16 3:25 ` Jens Axboe
2023-02-09 5:10 Christoph Hellwig
2023-02-09 15:12 ` Jens Axboe
2023-02-02 15:23 Christoph Hellwig
2023-02-02 18:02 ` Jens Axboe
2023-01-20 5:52 Christoph Hellwig
2023-01-20 15:09 ` Jens Axboe
2023-01-12 8:25 Christoph Hellwig
2023-01-12 17:37 ` Jens Axboe
2022-12-29 16:41 Christoph Hellwig
2022-12-29 18:32 ` Jens Axboe
2022-12-22 15:43 Christoph Hellwig
2022-12-22 16:23 ` 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=6bea4ea1-9dac-6d74-c3b8-54982fd3de66@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