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 5.12
Date: Thu, 11 Feb 2021 11:31:58 -0700 [thread overview]
Message-ID: <d76200cd-1ab2-8ac5-31b6-388db44bef3b@kernel.dk> (raw)
In-Reply-To: <YCV0PmcdMDOeQp5Q@infradead.org>
On 2/11/21 11:15 AM, Christoph Hellwig wrote:
> Note that we have some issues with the previous updates. We're working
> fast on fixes for those, but in the meantime I think it is good to get
> these changes out to you and into linux-next.
Pulled - it throws a trivial reject in the quirks list, fwiw.
--
Jens Axboe
next prev parent reply other threads:[~2021-02-11 18:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-11 18:15 [GIT PULL] second round of nvme updates for 5.12 Christoph Hellwig
2021-02-11 18:31 ` Jens Axboe [this message]
2021-02-11 18:33 ` Christoph Hellwig
2021-02-11 18:34 ` 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=d76200cd-1ab2-8ac5-31b6-388db44bef3b@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