From: Angelo Dureghello <angelo@sysam.it>
To: Vinod <vkoul@kernel.org>
Cc: dmaengine@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: [v7,1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)
Date: Tue, 3 Jul 2018 15:39:54 +0200 [thread overview]
Message-ID: <20180703133953.GA9939@jerusalem> (raw)
Hi Vinod,
On Tue, Jul 03, 2018 at 06:00:14PM +0530, Vinod wrote:
> On 03-07-18, 12:37, Angelo Dureghello wrote:
> > This patch adds a new fsl-edma-common module to allow new
> > mcf-edma module code to use most of the fsl-edma code.
> >
> > Due to some differences between ColdFire edma (64 channels) and
> > fsl-edma (32 channels), as register set offsets and some other
> > points as the different interrupt organization and other minor
> > things, a common module can collect most of the code for both
> > 32 and 64 channel edma module versions.
>
> ??
>
> You didn't see my email https://marc.info/?l=dmaengine&m=153060940829531&w=2
>
Ops, missed it. No prob, new patch follow with the 2 fixes.
Regards,
Angelo
> --
> ~Vinod
> --
> To unsubscribe from this list: send the line "unsubscribe dmaengine" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
---
To unsubscribe from this list: send the line "unsubscribe dmaengine" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-07-03 13:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-03 13:39 Angelo Dureghello [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-03 12:30 [v7,1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended) Vinod Koul
2018-07-03 10:37 Angelo Dureghello
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=20180703133953.GA9939@jerusalem \
--to=angelo@sysam.it \
--cc=dmaengine@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=vkoul@kernel.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).