From: Tejun Heo <tj@kernel.org>
To: Tom Yan <tom.ty89@gmail.com>
Cc: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
martin.petersen@oracle.com, linux-ide@vger.kernel.org,
linux-scsi@vger.kernel.org
Subject: Re: [PATCH v2 2/2] libata-scsi: do not respond with "invalid field" for FORMAT UNIT
Date: Wed, 6 Jul 2016 09:39:49 -0400 [thread overview]
Message-ID: <20160706133949.GE3262@mtj.duckdns.org> (raw)
In-Reply-To: <CAGnHSEnuCTP4R1EwB0UPW1S_=GzWjbaxyKW9JK7oKGMpzyrX7w@mail.gmail.com>
On Wed, Jul 06, 2016 at 06:40:32AM +0000, Tom Yan wrote:
> Um it's not mainly about in caps or not, but more about wrongly spelled as cbd.
Heh, right, so please just note it in the description.
Thanks.
--
tejun
prev parent reply other threads:[~2016-07-06 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160705064556.909-1-me>
2016-07-05 6:45 ` [PATCH v2 2/2] libata-scsi: do not respond with "invalid field" for FORMAT UNIT tom.ty89
2016-07-05 11:08 ` Sergei Shtylyov
2016-07-05 19:13 ` Tom Yan
2016-07-05 22:39 ` Tejun Heo
2016-07-06 6:40 ` Tom Yan
2016-07-06 13:39 ` 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=20160706133949.GE3262@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).