From: Jens Axboe <axboe@kernel.dk>
To: Christoph Hellwig <hch@infradead.org>
Cc: Keith Busch <kbusch@kernel.org>,
linux-block@vger.kernel.org, Sagi Grimberg <sagi@grimberg.me>,
linux-nvme@lists.infradead.org
Subject: Re: [GIT PULL] second round of nvme updates for Linux 5.16
Date: Thu, 28 Oct 2021 08:35:39 -0600 [thread overview]
Message-ID: <7b21a606-d582-ad3b-54d3-d8b8e7b247c8@kernel.dk> (raw)
In-Reply-To: <YXqzb6dj0DCrIbGY@infradead.org>
On 10/28/21 8:27 AM, Christoph Hellwig wrote:
> The following changes since commit d28e4dff085c5a87025c9a0a85fb798bd8e9ca17:
>
> block: ataflop: more blk-mq refactoring fixes (2021-10-25 07:54:32 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-5.16-2021-10-28
Pulled, thanks.
--
Jens Axboe
next prev parent reply other threads:[~2021-10-28 14:35 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 14:27 [GIT PULL] second round of nvme updates for Linux 5.16 Christoph Hellwig
2021-10-28 14:35 ` Jens Axboe [this message]
2021-10-29 10:19 ` Hannes Reinecke
2021-10-29 10:32 ` Hannes Reinecke
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=7b21a606-d582-ad3b-54d3-d8b8e7b247c8@kernel.dk \
--to=axboe@kernel.dk \
--cc=hch@infradead.org \
--cc=kbusch@kernel.org \
--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).