From: Timur Tabi <b04825@freescale.com>
To: "Ira W. Snyder" <iws@ovro.caltech.edu>
Cc: Dan Williams <dan.j.williams@intel.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 1/1] fsldma: ignore end of segments interrupt
Date: Thu, 16 Feb 2012 13:48:20 -0600 [thread overview]
Message-ID: <4F3D5D84.2040609@freescale.com> (raw)
In-Reply-To: <20120216194655.GD9262@ovro.caltech.edu>
Ira W. Snyder wrote:
> No. I don't have the ability to connect my P2020 up to an FPGA to
> recreate the DMA workload that causes this on my 8349EA. I can run the
> dmatest module, if you'd like.
I just want to make sure your patch doesn't break 85xx.
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2012-02-16 19:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 20:58 [PATCH 1/1] fsldma: ignore end of segments interrupt Ira W. Snyder
2012-01-31 21:30 ` [PATCH v2] " Ira W. Snyder
2012-02-16 17:50 ` [PATCH 1/1] " Tabi Timur-B04825
2012-02-16 19:00 ` Ira W. Snyder
2012-02-16 19:34 ` Timur Tabi
2012-02-16 19:46 ` Ira W. Snyder
2012-02-16 19:48 ` Timur Tabi [this message]
2012-02-17 0:57 ` Ira W. Snyder
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=4F3D5D84.2040609@freescale.com \
--to=b04825@freescale.com \
--cc=dan.j.williams@intel.com \
--cc=iws@ovro.caltech.edu \
--cc=linuxppc-dev@lists.ozlabs.org \
/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;
as well as URLs for NNTP newsgroup(s).