From: "Martin K. Petersen" <martin.petersen@oracle.com>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Thomas Bogendoerfer <tsbogend@alpha.franken.de>,
David Miller <davem@davemloft.net>,
Hannes Reinecke <hare@suse.com>, Meelis Roos <mroos@linux.ee>,
Michael Schmitz <schmitzmic@gmail.com>,
<linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/5] esp_scsi, mac_esp: Various fixes and cleanups
Date: Thu, 10 Aug 2017 19:59:42 -0400 [thread overview]
Message-ID: <yq18tir3rf5.fsf@oracle.com> (raw)
In-Reply-To: <cover.1501825111.git.fthain@telegraphics.com.au> (Finn Thain's message of "Fri, 4 Aug 2017 01:43:19 -0400 (EDT)")
Finn,
> This series has been tested on m68k Macs (ESP236 equivalent).
>
> Some more testing with different targets and devices (FAS236 etc)
> might be nice. Being that the esp_scsi fixes are on error paths, more
> review may actually be more valuable than more testing...
Applied to 4.14/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
prev parent reply other threads:[~2017-08-11 0:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-04 5:43 [PATCH 0/5] esp_scsi, mac_esp: Various fixes and cleanups Finn Thain
2017-08-04 5:43 ` [PATCH 1/5] scsi/mac_esp: Avoid type warning from sparse Finn Thain
2017-08-04 5:43 ` [PATCH 2/5] scsi/mac_esp: Fix PIO transfers for MESSAGE IN phase Finn Thain
2017-08-04 5:43 ` [PATCH 3/5] scsi/esp_scsi: Clean up control flow and dead code Finn Thain
2017-08-04 5:43 ` [PATCH 5/5] scsi/esp_scsi: Always clear msg_out_len after MESSAGE OUT phase Finn Thain
2017-08-04 5:43 ` [PATCH 4/5] scsi/esp_scsi: Avoid sending ABORT TASK SET messages Finn Thain
2017-08-10 23:59 ` Martin K. Petersen [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=yq18tir3rf5.fsf@oracle.com \
--to=martin.petersen@oracle.com \
--cc=davem@davemloft.net \
--cc=fthain@telegraphics.com.au \
--cc=hare@suse.com \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=mroos@linux.ee \
--cc=schmitzmic@gmail.com \
--cc=tsbogend@alpha.franken.de \
/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