All of lore.kernel.org
 help / color / mirror / Atom feed
From: Phillip Susi <psusi@ubuntu.com>
To: "Martin K. Petersen" <martin.petersen@oracle.com>
Cc: Tejun Heo <tj@kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] libata: Whitelist SSDs that are known to properly return zeroes after TRIM
Date: Wed, 03 Dec 2014 22:28:54 -0500	[thread overview]
Message-ID: <547FD4F6.7090700@ubuntu.com> (raw)
In-Reply-To: <yq1sigwgkqt.fsf@sermon.lab.mkp.net>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On 12/03/2014 10:24 PM, Martin K. Petersen wrote:
> Well. It's a bit stronger than wishful thinking given that OEM
> product requirements documents and supply contracts make it so. But
> it is not something we can get in writing.

OEM product requirements documents and supply contracts sound like
forms of writing to me.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBCgAGBQJUf9T2AAoJENRVrw2cjl5Rc2IH/0f1txjITXL7Os4W2KqTUbFj
RryTH8pxexysy1flXcUT4nIyoulBnRSDsy6o9DTgPI5lZDgsIVzFaNuYJHBv/Z/n
mvnjPXS4gp1cFCogHZ6K1IbMQC2WBs7Hz+Qq9pxvLKBVuifcsF+4VOiCQtz7A6QR
nfkPRh9JP7cN0kjNLYVvoNfFDqSVJ8Ac2IbKkB3OeqmeuLoxpL1qG0fSE+A90/nB
B9/wVeFiw5nH6Fdyy6kodbt0tF+gwOGBFIynVKO+4E3qeZi28YikLN/m+L09mW/m
kW4UXXWDCLnqmrfxy/VTHCKUZruj9uplZ/3UpWl8vC4jJmZM5HYS7GNE+AJurjA=
=kslG
-----END PGP SIGNATURE-----

  reply	other threads:[~2014-12-04  3:28 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-04  2:44 [PATCH] libata: Whitelist SSDs that are known to properly return zeroes after TRIM Martin K. Petersen
2014-12-04  3:02 ` Phillip Susi
2014-12-04  3:24   ` Martin K. Petersen
2014-12-04  3:28     ` Phillip Susi [this message]
2014-12-04  3:35       ` Martin K. Petersen
2014-12-04  4:40         ` Phillip Susi
2014-12-05  1:53           ` Martin K. Petersen
2014-12-04 21:49         ` One Thousand Gnomes
2014-12-05  2:46           ` Martin K. Petersen
2014-12-04 17:06 ` Tejun Heo
2014-12-05  2:13   ` Martin K. Petersen
2014-12-05 14:51     ` Tejun Heo
2014-12-10  4:09       ` James Bottomley
2014-12-10 14:29         ` Tejun Heo
2014-12-10 20:34           ` James Bottomley
2014-12-10 21:02           ` Martin K. Petersen
2014-12-12  8:35             ` Ming Lei
2015-01-05 16:28             ` Tejun Heo
2015-01-07  0:05               ` Martin K. Petersen
2015-01-07  2:54                 ` Tejun Heo
2015-01-07  4:15                   ` Dave Chinner
2015-01-07 15:26                     ` Tejun Heo
2015-01-08 14:28                       ` Martin K. Petersen
2015-01-08 15:11                         ` Tejun Heo
2015-01-08 15:34                           ` Martin K. Petersen
2015-01-08 15:36                             ` Tejun Heo
2015-01-08 15:58                         ` Tim Small
2015-01-09 20:52                           ` Martin K. Petersen
2015-01-09 21:39                             ` Tejun Heo
2015-01-08 14:29                       ` Martin K. Petersen
2015-01-08  4:05                     ` Phillip Susi
2015-01-08  4:58                       ` Andreas Dilger
2015-01-08 14:09                         ` Phillip Susi
2015-01-08 22:31                           ` Andreas Dilger
2014-12-10 15:43         ` Tim Small

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=547FD4F6.7090700@ubuntu.com \
    --to=psusi@ubuntu.com \
    --cc=linux-ide@vger.kernel.org \
    --cc=martin.petersen@oracle.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 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.