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] first round of nvme updates for Linux 6.1
Date: Tue, 20 Sep 2022 07:50:56 -0600 [thread overview]
Message-ID: <c296189b-0a43-e682-d5c1-85cec7ce1f98@kernel.dk> (raw)
In-Reply-To: <Yylz9ST3BJeXmQCU@infradead.org>
On 9/20/22 2:04 AM, Christoph Hellwig wrote:
> Hi Jens,
>
> here is currently queue up nvme patches for 6.1, which are not a lot.
> There are a few more patches under discussion that will follow later.
>
> The following changes since commit 91418cc4fd8f8e2e21b409eb8983d074359c8be6:
>
> block/drbd: remove unused w_start_resync declaration (2022-09-12 01:47:57 -0600)
>
> are available in the Git repository at:
>
> git://git.infradead.org/nvme.git tags/nvme-6.1-2022-09-20
Pulled, thanks.
--
Jens Axboe
prev parent reply other threads:[~2022-09-20 13:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-20 8:04 [GIT PULL] first round of nvme updates for Linux 6.1 Christoph Hellwig
2022-09-20 13:50 ` Jens Axboe [this message]
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=c296189b-0a43-e682-d5c1-85cec7ce1f98@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