From: Ondrej Zary <linux@rainbow-software.org>
To: Finn Thain <fthain@telegraphics.com.au>
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 0/4] g_NCR5380: PDMA fixes and cleanup
Date: Thu, 22 Jun 2017 23:11:37 +0200 [thread overview]
Message-ID: <201706222311.38121.linux@rainbow-software.org> (raw)
In-Reply-To: <cover.1497528687.git.fthain@telegraphics.com.au>
On Thursday 15 June 2017 14:17:56 Finn Thain wrote:
> Ondrej, would you please test this patch series? One of your patches
> has been modified slightly and the two I wrote are untested.
Works only with HDD on non-DTC chips. CD-ROM hangs. DTC hangs even with HDD.
The PDMA code really needs to be fixed.
--
Ondrej Zary
next prev parent reply other threads:[~2017-06-22 21:11 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-15 12:17 [PATCH 0/4] g_NCR5380: PDMA fixes and cleanup Finn Thain
2017-06-15 12:17 ` Finn Thain
2017-06-15 12:17 ` [PATCH 3/4] g_NCR5380: Limit sg_tablesize to avoid PDMA read overruns on DTC436 Finn Thain
2017-06-15 12:17 ` Finn Thain
2017-06-15 12:17 ` [PATCH 4/4] g_NCR5380: Cleanup comments and whitespace Finn Thain
2017-06-15 12:17 ` Finn Thain
2017-06-15 12:17 ` [PATCH 1/4] g_NCR5380: Fix PDMA transfer size Finn Thain
2017-06-15 12:17 ` Finn Thain
2017-06-15 12:17 ` [PATCH 2/4] g_NCR5380: End PDMA transfer correctly on target disconnection Finn Thain
2017-06-15 12:17 ` Finn Thain
2017-06-22 21:11 ` Ondrej Zary [this message]
2017-06-23 1:06 ` [PATCH 0/4] g_NCR5380: PDMA fixes and cleanup Finn Thain
2017-06-23 11:01 ` Finn Thain
2017-06-23 20:13 ` Ondrej Zary
2017-06-24 2:50 ` Finn Thain
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=201706222311.38121.linux@rainbow-software.org \
--to=linux@rainbow-software.org \
--cc=fthain@telegraphics.com.au \
--cc=jejb@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.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 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.