From: Keith Busch <kbusch@kernel.org>
To: Lach <iam@lach.pw>
Cc: axboe@fb.com, linux-kernel@vger.kernel.org, hch@lst.de,
linux-nvme@lists.infradead.org, sagi@grimberg.me
Subject: Re: Regression in nvme driver
Date: Wed, 29 Jul 2020 12:49:29 -0700 [thread overview]
Message-ID: <20200729194929.GA3499289@dhcp-10-100-145-180.wdl.wdc.com> (raw)
In-Reply-To: <8aeb9192-df1b-979d-514d-025366f658e2@lach.pw>
On Wed, Jul 29, 2020 at 07:29:08PM +0000, Lach wrote:
> Hello
>
> I caught a regression in the nvme driver, which shows itself on some
> controllers (In my case, at 126h:2263)
Fix is staged for the next 5.8 pull;
https://git.kernel.dk/cgit/linux-block/commit/?h=block-5.8&id=5bedd3afee8eb01ccd256f0cd2cc0fa6f841417a
_______________________________________________
Linux-nvme mailing list
Linux-nvme@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-nvme
parent reply other threads:[~2020-07-29 19:49 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <8aeb9192-df1b-979d-514d-025366f658e2@lach.pw>]
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=20200729194929.GA3499289@dhcp-10-100-145-180.wdl.wdc.com \
--to=kbusch@kernel.org \
--cc=axboe@fb.com \
--cc=hch@lst.de \
--cc=iam@lach.pw \
--cc=linux-kernel@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).