From: Hongbo Zhang <hongbo.zhang@freescale.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: 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 3/7] DMA: Freescale: add fsl_dma_free_descriptor() to reduce code duplication
Date: Fri, 28 Mar 2014 11:44:34 +0800 [thread overview]
Message-ID: <5334F022.3050402@freescale.com> (raw)
In-Reply-To: <20140311110616.GV1976@intel.com>
On 03/11/2014 07:06 PM, Vinod Koul wrote:
> On Thu, Jan 16, 2014 at 01:47:22PM +0800, hongbo.zhang@freescale.com wrote:
>> From: Hongbo Zhang <hongbo.zhang@freescale.com>
>>
>> There are several places where descriptors are freed using identical code.
>> This patch puts this code into a function to reduce code duplication.
>>
>> Signed-off-by: Hongbo Zhang <hongbo.zhang@freescale.com>
>> Signed-off-by: Qiang Liu <qiang.liu@freescale.com>
>> ---
>> drivers/dma/fsldma.c | 38 ++++++++++++++++++++------------------
>> 1 file changed, 20 insertions(+), 18 deletions(-)
>>
>> diff --git a/drivers/dma/fsldma.c b/drivers/dma/fsldma.c
>> index 95236e6..ad73538 100644
>> --- a/drivers/dma/fsldma.c
>> +++ b/drivers/dma/fsldma.c
>> @@ -418,6 +418,21 @@ static dma_cookie_t fsl_dma_tx_submit(struct dma_async_tx_descriptor *tx)
>> }
>>
>> /**
>> + * fsl_dma_free_descriptor - Free descriptor from channel's DMA pool.
>> + * @chan : Freescale DMA channel
>> + * @desc: descriptor to be freed
>> + */
>> +static void fsl_dma_free_descriptor(struct fsldma_chan *chan,
>> + struct fsl_desc_sw *desc)
>> +{
>> + list_del(&desc->node);
>> +#ifdef FSL_DMA_LD_DEBUG
>> + chan_dbg(chan, "LD %p free\n", desc);
>> +#endif
> why not wrap the define stuff in the defination of chan_dbg rather than its
> usage :(
>
OK, I will fix it by another separate patch.
Thanks.
next prev parent reply other threads:[~2014-03-28 3:44 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 [this message]
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 ` [PATCH 0/7] DMA: Freescale: driver cleanups and enhancements Hongbo Zhang
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=5334F022.3050402@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).