From: Tejun Heo <tj@kernel.org>
To: tom.ty89@gmail.com
Cc: martin.petersen@oracle.com, sergei.shtylyov@cogentembedded.com,
linux-ide@vger.kernel.org, linux-scsi@vger.kernel.org
Subject: Re: [PATCH resend 1/2] libata-scsi: do not respond with "invalid field" for FORMAT UNIT
Date: Wed, 6 Jul 2016 13:32:34 -0400 [thread overview]
Message-ID: <20160706173234.GA4065@mtj.duckdns.org> (raw)
In-Reply-To: <577d3c35.949b620a.2f8b5.ffffb1c4@mx.google.com>
On Thu, Jul 07, 2016 at 01:13:08AM +0800, tom.ty89@gmail.com wrote:
> From: Tom Yan <tom.ty89@gmail.com>
>
> It does not make sense and is confusing to respond with "Invalid
> field in CDB" while we have no support at all implemented for
> FORMAT UNIT. It is decent to let it go to the default, which
> will respond with "Invalid command operation code" instead.
>
> Signed-off-by: Tom Yan <tom.ty89@gmail.com>
Applied to libata/for-4.8.
Thanks.
--
tejun
prev parent reply other threads:[~2016-07-06 17:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 17:13 [PATCH resend 1/2] libata-scsi: do not respond with "invalid field" for FORMAT UNIT tom.ty89
2016-07-06 17:32 ` Tejun Heo [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=20160706173234.GA4065@mtj.duckdns.org \
--to=tj@kernel.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=tom.ty89@gmail.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).