All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 23 Jun 2017 22:13:59 +0200	[thread overview]
Message-ID: <201706232214.00362.linux@rainbow-software.org> (raw)
In-Reply-To: <alpine.LNX.2.00.1706232058220.10492@nippy.intranet>

On Friday 23 June 2017 13:01:53 Finn Thain wrote:
> On Fri, 23 Jun 2017, I wrote:
> > Does this patch help? It should be applied on top of this series of 4.
>
> Sorry, I sent the wrong diff. Please try this patch instead.

Thanks, much better now: both HDD and CD-ROM seem to work on DTC and non-DTC 
chips. I get many of these messages with CD-ROM:
[  912.397076] generic_NCR5380_pread: No end dma signal (4096/4096)
[  913.141225] generic_NCR5380_pread: No end dma signal (4096/4096)

Maybe just remove this error message as in my original patch?

-- 
Ondrej Zary

  reply	other threads:[~2017-06-23 20:13 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 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-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-22 21:11 ` [PATCH 0/4] g_NCR5380: PDMA fixes and cleanup Ondrej Zary
2017-06-23  1:06   ` Finn Thain
2017-06-23 11:01     ` Finn Thain
2017-06-23 20:13       ` Ondrej Zary [this message]
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=201706232214.00362.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.