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 updates for Linux 6.2
Date: Wed, 7 Dec 2022 12:40:29 -0700 [thread overview]
Message-ID: <3747bc85-967c-fd5a-66e5-7cad42d00bcd@kernel.dk> (raw)
In-Reply-To: <Y5DbMySCBMWI7CbE@infradead.org>
On 12/7/22 11:28 AM, Christoph Hellwig wrote:
> The following changes since commit eea3e8b74aa1648fc96b739458d067a6e498c302:
>
> blk-throttle: Use more suitable time_after check for update of slice_start (2022-12-05 13:45:31 -0700)
>
> are available in the Git repository at:
>
> ssh://git.infradead.org/var/lib/git/nvme.git tags/nvme-6.2-2022-12-07
I pulled:
git://git.infradead.org/nvme tags/nvme-6.2-2022-12-07
--
Jens Axboe
next prev parent reply other threads:[~2022-12-07 19:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 18:28 [GIT PULL] nvme updates for Linux 6.2 Christoph Hellwig
2022-12-07 19:40 ` Jens Axboe [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-29 8:56 Christoph Hellwig
2022-11-29 13:56 ` 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=3747bc85-967c-fd5a-66e5-7cad42d00bcd@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