All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Dave Jones <davej@codemonkey.org.uk>
Cc: linux-scsi@vger.kernel.org, Quinn Tran <quinn.tran@cavium.com>
Subject: Re: scsi: qla2xxx: Fix apparent cut-n-paste error.
Date: Thu, 05 Jan 2017 20:52:07 -0500	[thread overview]
Message-ID: <yq1bmvlhs54.fsf@oracle.com> (raw)
In-Reply-To: <20161227181321.35xf5hm4qz3uajmp@codemonkey.org.uk> (Dave Jones's message of "Tue, 27 Dec 2016 13:13:21 -0500")

>>>>> "Dave" == Dave Jones <davej@codemonkey.org.uk> writes:

Dave> commit 093df73771bac8a37d607c0e705d157a8cef4c5c introduces two
Dave> bodies of code that look similar but with s/req/rsp/ in the second
Dave> instance.  But in one case, it looks like this conversion was
Dave> missed.

Quinn?

-- 
Martin K. Petersen	Oracle Linux Engineering

  parent reply	other threads:[~2017-01-06  1:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-27 18:13 scsi: qla2xxx: Fix apparent cut-n-paste error Dave Jones
2016-12-28 17:00 ` Laurence Oberman
2017-01-06  1:52 ` Martin K. Petersen [this message]
2017-01-09 18:43   ` Tran, Quinn
2017-01-10  4:24 ` 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=yq1bmvlhs54.fsf@oracle.com \
    --to=martin.petersen@oracle.com \
    --cc=davej@codemonkey.org.uk \
    --cc=linux-scsi@vger.kernel.org \
    --cc=quinn.tran@cavium.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 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.