From: Finn Thain <fthain@telegraphics.com.au>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Schmitz <schmitzmic@gmail.com>
Subject: Re: [PATCH v7 0/6] g_NCR5380: PDMA fixes and cleanup
Date: Wed, 5 Jul 2017 10:40:37 +1000 (AEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1707051040280.2194@nippy.intranet> (raw)
In-Reply-To: <201707042254.20791.linux@rainbow-software.org>
On Tue, 4 Jul 2017, Ondrej Zary wrote:
>
> Everything works fine! No corruption, no hangs, rescan-scsi-bus works.
>
> Tested cards:
> Canon FG2-5202 (53C400 chip, MMIO)
> DTC-3181L (DTCT-436P chip, PIO)
> HP C2502 (53C400A chip, PIO)
>
> Tested devices:
> QUANTUM LP240S GM240S01X 4.6
> IBM DORS-32160 WA0A
> SONY CD-ROM CDU-415 1.1g
> SONY CD-ROM CDU-55S 1.0t
>
> Tested-by: Ondrej Zary <linux@rainbow-software.org>
>
Great! Thanks for testing all of those revisions.
--
next prev parent reply other threads:[~2017-07-05 0:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 7:59 Finn Thain
2017-07-03 7:59 ` [PATCH v7 1/6] g_NCR5380: Fix PDMA transfer size Finn Thain
2017-07-03 7:59 ` [PATCH v7 2/6] g_NCR5380: End PDMA transfer correctly on target disconnection Finn Thain
2017-07-03 7:59 ` [PATCH v7 4/6] g_NCR5380: Use unambiguous terminology for PDMA send and receive Finn Thain
2017-07-03 7:59 ` [PATCH v7 5/6] g_NCR5380: Re-work PDMA loops Finn Thain
2017-07-03 7:59 ` [PATCH v7 6/6] g_NCR5380: Two DTC436 PDMA workarounds Finn Thain
2017-07-03 7:59 ` [PATCH v7 3/6] g_NCR5380: Cleanup comments and whitespace Finn Thain
2017-07-04 20:54 ` [PATCH v7 0/6] g_NCR5380: PDMA fixes and cleanup Ondrej Zary
2017-07-05 0:40 ` Finn Thain [this message]
2017-07-12 21:40 ` 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=alpine.LNX.2.00.1707051040280.2194@nippy.intranet \
--to=fthain@telegraphics.com.au \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=martin.petersen@oracle.com \
--cc=schmitzmic@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
all inboxes | Powered by JetHome®