From: Finn Thain <fthain@telegraphics.com.au>
To: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Ondrej Zary <linux@rainbow-software.org>
Cc: linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org,
Michael Schmitz <schmitzmic@gmail.com>
Subject: [PATCH v2 0/5] g_NCR5380: PDMA fixes and cleanup
Date: Sat, 24 Jun 2017 02:37:36 -0400 (EDT) [thread overview]
Message-ID: <cover.1498285948.git.fthain@telegraphics.com.au> (raw)
Ondrej, would you please test this new series?
Changed since v1:
- PDMA transfer residual is calculated earlier.
- End of DMA flag check is now polled (if there is any residual).
Finn Thain (2):
g_NCR5380: Limit sg_tablesize to avoid PDMA read overruns on DTC436
g_NCR5380: Cleanup comments and whitespace
Ondrej Zary (3):
g_NCR5380: Fix PDMA transfer size
g_NCR5380: End PDMA transfer correctly on target disconnection
g_NCR5380: Re-work PDMA loops
drivers/scsi/g_NCR5380.c | 231 ++++++++++++++++++++++-------------------------
1 file changed, 107 insertions(+), 124 deletions(-)
--
2.13.0
WARNING: multiple messages have this Message-ID (diff)
From: Finn Thain <fthain@telegraphics.com.au>
To: "James E.J. Bottomley" <jejb@linux.vnet.ibm.com>,
"Martin K. Petersen" <martin.petersen@oracle.com>,
Ondrej Zary <linux@rainbow-software.org>
Cc: <linux-scsi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Michael Schmitz <schmitzmic@gmail.com>
Subject: [PATCH v2 0/5] g_NCR5380: PDMA fixes and cleanup
Date: Sat, 24 Jun 2017 02:37:36 -0400 (EDT) [thread overview]
Message-ID: <cover.1498285948.git.fthain@telegraphics.com.au> (raw)
Ondrej, would you please test this new series?
Changed since v1:
- PDMA transfer residual is calculated earlier.
- End of DMA flag check is now polled (if there is any residual).
Finn Thain (2):
g_NCR5380: Limit sg_tablesize to avoid PDMA read overruns on DTC436
g_NCR5380: Cleanup comments and whitespace
Ondrej Zary (3):
g_NCR5380: Fix PDMA transfer size
g_NCR5380: End PDMA transfer correctly on target disconnection
g_NCR5380: Re-work PDMA loops
drivers/scsi/g_NCR5380.c | 231 ++++++++++++++++++++++-------------------------
1 file changed, 107 insertions(+), 124 deletions(-)
--
2.13.0
next reply other threads:[~2017-06-24 6:37 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-24 6:37 Finn Thain [this message]
2017-06-24 6:37 ` [PATCH v2 0/5] g_NCR5380: PDMA fixes and cleanup Finn Thain
2017-06-24 6:37 ` [PATCH v2 1/5] g_NCR5380: Fix PDMA transfer size Finn Thain
2017-06-24 6:37 ` Finn Thain
2017-06-24 6:37 ` [PATCH v2 2/5] g_NCR5380: End PDMA transfer correctly on target disconnection Finn Thain
2017-06-24 6:37 ` Finn Thain
2017-06-24 6:37 ` [PATCH v2 3/5] g_NCR5380: Limit sg_tablesize to avoid PDMA read overruns on DTC436 Finn Thain
2017-06-24 6:37 ` Finn Thain
2017-06-24 6:37 ` [PATCH v2 5/5] g_NCR5380: Re-work PDMA loops Finn Thain
2017-06-24 6:37 ` Finn Thain
2017-06-24 6:37 ` [PATCH v2 4/5] g_NCR5380: Cleanup comments and whitespace Finn Thain
2017-06-24 6:37 ` Finn Thain
2017-06-25 9:26 ` [PATCH v2 0/5] g_NCR5380: PDMA fixes and cleanup Ondrej Zary
2017-06-26 7:35 ` Finn Thain
2017-06-26 8:20 ` Ondrej Zary
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=cover.1498285948.git.fthain@telegraphics.com.au \
--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 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.