From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: linux-omap@vger.kernel.org,
linux-omap-open-source <linux-omap-open-source@linux.omap.com>
Subject: Re: [PATCH] ARM: OMAP: Fix chain_a_transfer return value
Date: Sat, 15 Dec 2007 16:28:11 -0800 [thread overview]
Message-ID: <20071216002811.GE7388@atomide.com> (raw)
In-Reply-To: <010C7BAE6783F34D9AC336EE5A01A0880506667C@dbde01.ent.ti.com>
* Gadiyar, Anand <gadiyar@ti.com> [071214 04:51]:
> From: Anand Gadiyar <gadiyar@ti.com>
>
> This patch changes the return value of omap_dma_chain_a_transfer
> to 0 on success instead of the flag 'start_dma', which wasn't really useful
> for anything.
>
> Signed-off-by: Anand Gadiyar <gadiyar@ti.com>
> Index: linux-omap-dec10/arch/arm/plat-omap/dma.c
> ===================================================================
> --- linux-omap-dec10.orig/arch/arm/plat-omap/dma.c 2007-12-10 11:01:38.000000000 +0530
> +++ linux-omap-dec10/arch/arm/plat-omap/dma.c 2007-12-13 16:54:25.378626162 +0530
> @@ -1254,7 +1254,7 @@
> * @param frame_count
> * @param callbk_data - channel callback parameter data.
> *
> - * @return - Success : start_dma status
> + * @return - Success : 0
> * Failure: -EINVAL/-EBUSY
> */
> int omap_dma_chain_a_transfer(int chain_id, int src_start, int dest_start,
> @@ -1375,7 +1375,7 @@
> dma_chan[lch].flags |= OMAP_DMA_ACTIVE;
> }
> }
> - return start_dma;
> + return 0;
> }
> EXPORT_SYMBOL(omap_dma_chain_a_transfer);
Pushing today.
Tony
next prev parent reply other threads:[~2007-12-16 0:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-14 12:50 [PATCH] ARM: OMAP: Fix chain_a_transfer return value Gadiyar, Anand
2007-12-16 0:28 ` Tony Lindgren [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-03-11 6:40 Gadiyar, Anand
2008-03-11 15:21 ` Tony Lindgren
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=20071216002811.GE7388@atomide.com \
--to=tony@atomide.com \
--cc=gadiyar@ti.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=linux-omap@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