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, 9 Feb 2023 08:12:28 -0700 [thread overview]
Message-ID: <d3529d65-f505-a76a-7f3c-db1d8d2578a3@kernel.dk> (raw)
In-Reply-To: <Y+SAN97vxJtL/l4G@infradead.org>
On 2/8/23 10:10 PM, Christoph Hellwig wrote:
> The following changes since commit e02bbac74cdde25f71a80978f5daa1d8a0aa6fc3:
>
> Merge tag 'nvme-6.2-2023-02-02' of git://git.infradead.org/nvme into block-6.2 (2023-02-02 11:02:12 -0700)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.2-2023-02-09
>
> for you to fetch changes up to 70daa5c8f001e351af174c40ac21eb0a25600483:
>
> nvme-auth: mark nvme_auth_wq static (2023-02-08 07:28:16 +0100)
>
> ----------------------------------------------------------------
> nvme fixes for Linux 6.2
>
> - fix a static checker warning for a variable introduces in the last
> pull request (Tom Rix)
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2023-02-09 15:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 5:10 [GIT PULL] nvme fixes for Linux 6.2 Christoph Hellwig
2023-02-09 15:12 ` 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-02 15:23 Christoph Hellwig
2023-02-02 18:02 ` Jens Axboe
2023-01-26 17:38 Christoph Hellwig
2023-01-26 18:44 ` 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=d3529d65-f505-a76a-7f3c-db1d8d2578a3@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).