From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Sudip Mukherjee <sudipm.mukherjee@gmail.com>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Tejun Heo <tj@kernel.org>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] libata: blacklist Micron 500IT SSD with MU01 firmware
Date: Thu, 05 Apr 2018 16:36:13 -0400 [thread overview]
Message-ID: <yq1po3d8k76.fsf@oracle.com> (raw)
In-Reply-To: <20180405203239.GA20090@sudip-laptop> (Sudip Mukherjee's message of "Thu, 5 Apr 2018 21:32:39 +0100")
Sudip,
> Any reply from Micron yet?
No, let me poke them again.
> It might be better and safe to blacklist all Micron SSDs except M500DC
> and M500IT (with MG02 firmware) until Micron replies.
Yeah, let's do that if I don't hear back within a day or two.
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2018-04-05 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-16 14:33 [PATCH] libata: blacklist Micron 500IT SSD with MU01 firmware Sudip Mukherjee
2018-03-16 15:54 ` Martin K. Petersen
2018-03-16 20:55 ` Sudip Mukherjee
2018-03-16 21:49 ` Martin K. Petersen
2018-04-05 20:32 ` Sudip Mukherjee
2018-04-05 20:36 ` Martin K. Petersen [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=yq1po3d8k76.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=sudipm.mukherjee@gmail.com \
--cc=tj@kernel.org \
/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