From: Jiri Slaby <jslaby@suse.cz>
To: Ben Hutchings <ben@decadent.org.uk>, stable <stable@vger.kernel.org>
Cc: "Martin K. Petersen" <martin.petersen@oracle.com>,
Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH stable 1/2] libata: Update Crucial/Micron blacklist
Date: Tue, 26 May 2015 10:18:58 +0200 [thread overview]
Message-ID: <55642C72.2090505@suse.cz> (raw)
In-Reply-To: <1432248698.12412.43.camel@decadent.org.uk>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
On 05/22/2015, 12:51 AM, Ben Hutchings wrote:
> From: "Martin K. Petersen" <martin.petersen@oracle.com> Date: Fri,
> 27 Mar 2015 15:17:20 -0400
>
> commit ff7f53fb82a7801a778e5902bdbbc5e195ab0de0 upstream.
>
> Micron has released an updated firmware (MU02) for M510/M550/MX100
> drives to fix the issues with queued TRIM. Queued TRIM remains
> broken on M500 but is working fine on later drives such as M600 and
> MX200.
>
> Tweak our blacklist to reflect the above.
>
> Link: https://bugzilla.kernel.org/show_bug.cgi?id=71371
> Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
> Signed-off-by: Tejun Heo <tj@kernel.org> [bwh: Backported to 3.16:
> adjust context and drop ZERO_AFTER_TRIM flags] Signed-off-by; Ben
> Hutchings <ben@decadent.org.uk> --- This appears to be needed for
> 3.12-3.18 stable branches, although 3.12.y already has the
> following patch and will therefore need further context changes.
Yes, tuned and pushed to 3.12. Thanks.
- --
js
suse labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
iQIcBAEBCAAGBQJVZCxyAAoJEL0lsQQGtHBJxZ4P/itrDyljIfo5Z2R4RfiViB2D
C/qL4IRymU8zBFg6kcFXhEhx0dfw2AxwYq+FqX8al90kXz9QmuG/sSJxCpeeomHv
lzIZjxWsILLrybiP1Vh0fnuzi85rfvzLHXEA+o1AGfOx99RBz4LKAP3qRilwQWt1
ONwX+ZyT+W1ngX+mu3bvxgYwVn4+EH9JLEMcaABrHhcLaaJmv9Tcotegz5aV7uML
19uBsl/9Z2jpX1mVpbgECjXHa59jzGB7jN5tczmWc9SNYnWK5TInXthAPMy9THF7
KjApE0A+bg0IjaHlM/9MNUM1vsfk0W4ytxWMsN0jMZTvuKINMXD57MUBfdrJlJjG
DzFw6rofdnUtId3DUWg9Q7K63E/j2GqF9LWWiqTfbhGskSP4dXfwqaTjw0vjGeIQ
zfsDjYuEHbOR45hIhmH8hsV834VZajMLrv6YwCaarvvmm28aSjYJef2JZkOTzHIE
fK1lUrMA/SwmxKYXVRRAQKzgUJDscsU6a6eJjmTPYqZIGb4layyGaLyJThkiZLSb
vWJilnJPvNMlIl8HYTi6VUrxQc5Rjd2lM8mLvpNGQxFNQSTbyw/GrCrFMqmd3Enc
c0xBqyYrPwmh9AnPpc0dlPwdWy7o0h63NmQrh3UISaaxxjrg8ihyPOv3pkrDdRwE
fZI4Ji9QotOqD/jRUsq6
=Rpsm
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2015-05-26 8:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-21 22:51 [PATCH stable 1/2] libata: Update Crucial/Micron blacklist Ben Hutchings
2015-05-21 22:54 ` [PATCH stable 2/2] libata: Blacklist queued TRIM on Samsung SSD 850 Pro Ben Hutchings
2015-05-26 8:18 ` Jiri Slaby
2015-05-25 12:55 ` [PATCH stable 1/2] libata: Update Crucial/Micron blacklist Luis Henriques
2015-05-26 8:18 ` Jiri Slaby [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=55642C72.2090505@suse.cz \
--to=jslaby@suse.cz \
--cc=ben@decadent.org.uk \
--cc=martin.petersen@oracle.com \
--cc=stable@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.