From: James Smart <jsmart2021@gmail.com>
To: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>,
james.bottomley@hansenpartnership.com
Cc: martin.petersen@oracle.com, linux-scsi@vger.kernel.org
Subject: Re: [PATCH] scsi: fix typos and grammar in comments of scsi_transport_fc.c
Date: Wed, 21 Jun 2017 13:48:38 -0700 [thread overview]
Message-ID: <0e776bd1-bf07-2ff6-4086-b29ce3a3d6fe@gmail.com> (raw)
In-Reply-To: <1498076679-8892-1-git-send-email-tyreld@linux.vnet.ibm.com>
On 6/21/2017 1:24 PM, Tyrel Datwyler wrote:
> Signed-off-by: Tyrel Datwyler <tyreld@linux.vnet.ibm.com>
> ---
> drivers/scsi/scsi_transport_fc.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
Reviewed-by: James Smart <james.smart@broadcom.com>
next prev parent reply other threads:[~2017-06-21 20:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 20:24 [PATCH] scsi: fix typos and grammar in comments of scsi_transport_fc.c Tyrel Datwyler
2017-06-21 20:48 ` James Smart [this message]
2017-06-26 17:23 ` Martin K. Petersen
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=0e776bd1-bf07-2ff6-4086-b29ce3a3d6fe@gmail.com \
--to=jsmart2021@gmail.com \
--cc=james.bottomley@hansenpartnership.com \
--cc=linux-scsi@vger.kernel.org \
--cc=martin.petersen@oracle.com \
--cc=tyreld@linux.vnet.ibm.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).