From: Vinod Koul <vinod.koul@intel.com>
To: hongbo.zhang@freescale.com
Cc: leo.li@freescale.com, vkoul@infradead.org,
linux-kernel@vger.kernel.org, scottwood@freescale.com,
dmaengine@vger.kernel.org, dan.j.williams@intel.com,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v5 0/3] DMA: Freescale: driver cleanups and enhancements
Date: Mon, 14 Jul 2014 21:35:26 +0530 [thread overview]
Message-ID: <20140714160526.GL2296@intel.com> (raw)
In-Reply-To: <1400659383-6555-1-git-send-email-hongbo.zhang@freescale.com>
On Wed, May 21, 2014 at 04:03:00PM +0800, hongbo.zhang@freescale.com wrote:
> From: Hongbo Zhang <hongbo.zhang@freescale.com>
>
> Hi Dan,
> Please have a look at this 3/3 as Vinod mentioned.
>
> Hi Vinod Koul,
> Please have a look at the v5 patch set.
I dont see any objection, so applying all 3 with subject changed to reflect
correct subsystem name
--
~Vinod
>
> v4 -> v5 changes:
> - since previous 5 of 8 patches have been merged by Vinod, this iteration oly
> inludes the last 3 patches of v4.
> - patches order is changed for being reviewed and merged easier.
> - remove the .prepare functions, and use the suspend_late and resume_early in
> the suspend-and-resume patch.
>
> v3 -> v4 changes:
> - Fixed a typo in [2/8] commit message.
> - There was a potential double call of list_del() when apply [4/8] only,
> although this defect is removed again in later [6/8]. This version
> eliminates this problem by updating [4/8] and [6/8] slightly.
> - Updated [8/8] to use register access method introduced by [2/8]
>
> v2 -> v3 change:
> Only add "chan->pm_state = RUNNING" for patch[8/8].
>
> v1 -> v2 change:
> The only one change is introducing a new patch[1/7] to remove the unnecessary
> macro FSL_DMA_LD_DEBUG, thus the total patches number is 8 now (was 7)
>
> v1 notes:
> 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.
>
> Hongbo Zhang (3):
> DMA: Freescale: use spin_lock_bh instead of spin_lock_irqsave
> DMA: Freescale: add suspend resume functions for DMA driver
> DMA: Freescale: change descriptor release process for supporting
> async_tx
>
> drivers/dma/fsldma.c | 297 ++++++++++++++++++++++++++++++++++++++------------
> drivers/dma/fsldma.h | 32 +++++-
> 2 files changed, 260 insertions(+), 69 deletions(-)
>
> --
> 1.7.9.5
>
>
> --
> 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
--
prev parent reply other threads:[~2014-07-14 16:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 8:03 [PATCH v5 0/3] DMA: Freescale: driver cleanups and enhancements hongbo.zhang
2014-05-21 8:03 ` [PATCH v5 1/3] DMA: Freescale: use spin_lock_bh instead of spin_lock_irqsave hongbo.zhang
2014-05-21 8:03 ` [PATCH v5 2/3] DMA: Freescale: add suspend resume functions for DMA driver hongbo.zhang
2014-05-21 8:03 ` [PATCH v5 3/3] DMA: Freescale: change descriptor release process for supporting async_tx hongbo.zhang
2014-07-14 16:05 ` Vinod Koul [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=20140714160526.GL2296@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=hongbo.zhang@freescale.com \
--cc=leo.li@freescale.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=scottwood@freescale.com \
--cc=vkoul@infradead.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).