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.1
Date: Wed, 7 Dec 2022 08:55:53 -0700 [thread overview]
Message-ID: <a3829d8a-9db5-d92d-7e41-dbc59e092e38@kernel.dk> (raw)
In-Reply-To: <Y5CeoZZcOCYaS/P9@infradead.org>
On 12/7/22 7:09 AM, Christoph Hellwig wrote:
> The following changes since commit 899d2a05dc14733cfba6224083c6b0dd5a738590:
>
> nvme: fix SRCU protection of nvme_ns_head list (2022-11-30 14:37:46 +0100)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.1-2022-12-07
>
> for you to fetch changes up to 6f2d71524bcfdeb1fcbd22a4a92a5b7b161ab224:
>
> nvme initialize core quirks before calling nvme_init_subsystem (2022-12-06 09:05:59 +0100)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.1
>
> - initialize core quirks before calling nvme_init_subsystem
> (Pankaj Raghav)
>
> ----------------------------------------------------------------
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2022-12-07 15:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 14:09 [GIT PULL] nvme fixes for Linux 6.1 Christoph Hellwig
2022-12-07 15:55 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-12-02 9:35 Christoph Hellwig
2022-12-02 15:01 ` Jens Axboe
2022-10-27 13:47 Christoph Hellwig
2022-10-27 13:50 ` Jens Axboe
2022-10-20 8:57 Christoph Hellwig
2022-10-20 12:44 ` Jens Axboe
2022-10-12 11:43 Christoph Hellwig
2022-10-12 13:16 ` 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=a3829d8a-9db5-d92d-7e41-dbc59e092e38@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;
as well as URLs for NNTP newsgroup(s).