public inbox for dmaengine@vger.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: Angelo Dureghello <angelo@sysam.it>
Cc: dmaengine@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: [v6,1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended)
Date: Tue, 3 Jul 2018 14:46:37 +0530	[thread overview]
Message-ID: <20180703091637.GO22377@vkoul-mobl> (raw)

On 03-07-18, 10:52, Angelo Dureghello wrote:
> On Tue, Jul 03, 2018 at 11:19:25AM +0530, Vinod wrote:
> > On 01-07-18, 18:33, 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.
> > 
> > I have applied these, thanks.
> > 
> > While applying I saw a trailing whitespace error, have fixed that up as
> > below.
> > 
> Strange checkpatch.pl is not signalling it .. 
> 
> > Also, I saw sparse complain a lot, care to fix those too?
> > 
> 
> Sure. Can send a new version soon.

Not a new version as I have applied this, but updates on top of applied
changes

             reply	other threads:[~2018-07-03  9:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-03  9:16 Vinod Koul [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-07-03  8:52 [v6,1/2] dmaengine: fsl-edma: extract common fsl-edma code (no changes in behavior intended) Angelo Dureghello
2018-07-03  5:49 Vinod Koul
2018-07-01 16:33 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=20180703091637.GO22377@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=angelo@sysam.it \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-m68k@vger.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