linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Hongbo Zhang <hongbo.zhang@freescale.com>
To: <vinod.koul@intel.com>, <dan.j.williams@intel.com>,
	<dmaengine@vger.kernel.org>
Cc: scottwood@freescale.com, linuxppc-dev@lists.ozlabs.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/7] DMA: Freescale: driver cleanups and enhancements
Date: Wed, 26 Feb 2014 15:38:19 +0800	[thread overview]
Message-ID: <530D99EB.3090900@freescale.com> (raw)
In-Reply-To: <1389851246-8564-1-git-send-email-hongbo.zhang@freescale.com>

Hi Vinod,
How about these patches?
Thanks.


On 01/16/2014 01:47 PM, hongbo.zhang@freescale.com wrote:
> From: Hongbo Zhang <hongbo.zhang@freescale.com>
>
> Hi Vinod Koul and Dan Williams,
> Please have a look at these patches.
>
> Note that patch 2~6 had beed sent out for upstream before, but were together
> with other storage patches at that time, that was not easy for being reviewed
> and merged, so I send them separately this time.
>
> Thanks.
>
> Hongbo Zhang (7):
>    DMA: Freescale: unify register access methods
>    DMA: Freescale: remove attribute DMA_INTERRUPT of dmaengine
>    DMA: Freescale: add fsl_dma_free_descriptor() to reduce code
>      duplication
>    DMA: Freescale: move functions to avoid forward declarations
>    DMA: Freescale: change descriptor release process for supporting
>      async_tx
>    DMA: Freescale: use spin_lock_bh instead of spin_lock_irqsave
>    DMA: Freescale: add suspend resume functions for DMA driver
>
>   drivers/dma/fsldma.c |  592 ++++++++++++++++++++++++++++++++------------------
>   drivers/dma/fsldma.h |   33 ++-
>   2 files changed, 412 insertions(+), 213 deletions(-)
>

      parent reply	other threads:[~2014-02-26  7:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16  5:47 [PATCH 0/7] DMA: Freescale: driver cleanups and enhancements hongbo.zhang
2014-01-16  5:47 ` [PATCH 1/7] DMA: Freescale: unify register access methods hongbo.zhang
2014-01-16  5:47 ` [PATCH 2/7] DMA: Freescale: remove attribute DMA_INTERRUPT of dmaengine hongbo.zhang
2014-01-16  5:47 ` [PATCH 3/7] DMA: Freescale: add fsl_dma_free_descriptor() to reduce code duplication hongbo.zhang
2014-03-11 11:06   ` Vinod Koul
2014-03-28  3:44     ` Hongbo Zhang
2014-04-03  8:09       ` Hongbo Zhang
2014-01-16  5:47 ` [PATCH 4/7] DMA: Freescale: move functions to avoid forward declarations hongbo.zhang
2014-01-16  5:47 ` [PATCH 5/7] DMA: Freescale: change descriptor release process for supporting async_tx hongbo.zhang
2014-01-16  5:47 ` [PATCH 6/7] DMA: Freescale: use spin_lock_bh instead of spin_lock_irqsave hongbo.zhang
2014-03-26  7:01   ` Vinod Koul
2014-03-28  6:33     ` Hongbo Zhang
2014-03-29 13:45       ` Vinod Koul
2014-03-31  4:08         ` Hongbo Zhang
2014-04-02 16:35           ` Vinod Koul
2014-04-03  7:00             ` Hongbo Zhang
2014-01-16  5:47 ` [PATCH 7/7] DMA: Freescale: add suspend resume functions for DMA driver hongbo.zhang
2014-02-26  7:38 ` Hongbo Zhang [this message]

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=530D99EB.3090900@freescale.com \
    --to=hongbo.zhang@freescale.com \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=scottwood@freescale.com \
    --cc=vinod.koul@intel.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 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).