From: Ido Schimmel <idosch@mellanox.com>
To: Christoph Hellwig <hch@lst.de>
Cc: tj@kernel.org, xiaolong.ye@intel.com, mlxsw@mellanox.com,
michaelsh@mellanox.com, linux-ide@vger.kernel.org
Subject: Re: Regression due to "libata: implement SECURITY PROTOCOL IN/OUT"
Date: Sat, 26 Aug 2017 20:15:37 +0300 [thread overview]
Message-ID: <20170826171537.GA4755@shredder> (raw)
In-Reply-To: <20170824121804.GA14057@shredder.mtl.com>
On Thu, Aug 24, 2017 at 03:18:04PM +0300, Ido Schimmel wrote:
> On Thu, Aug 24, 2017 at 02:07:29PM +0200, Christoph Hellwig wrote:
> > What kind of device is this? Seems like we need to blacklist it
> > as it chokes when we tried to read the Identify Devіce Log.
>
> Is the below enough or do you need more info?
Ping?
next prev parent reply other threads:[~2017-08-26 17:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-24 11:29 Regression due to "libata: implement SECURITY PROTOCOL IN/OUT" Ido Schimmel
2017-08-24 12:07 ` Christoph Hellwig
2017-08-24 12:18 ` Ido Schimmel
2017-08-26 17:15 ` Ido Schimmel [this message]
2017-08-27 9:05 ` Christoph Hellwig
2017-08-27 10:53 ` Ido Schimmel
2017-08-27 17:03 ` Christoph Hellwig
2017-08-27 18:25 ` Ido Schimmel
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=20170826171537.GA4755@shredder \
--to=idosch@mellanox.com \
--cc=hch@lst.de \
--cc=linux-ide@vger.kernel.org \
--cc=michaelsh@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=tj@kernel.org \
--cc=xiaolong.ye@intel.com \
/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).