From: Vinod Koul <vinod.koul@intel.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Dan Williams <dan.j.williams@intel.com>,
linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: manual merge of the dmaengine tree with the slave-dma tree
Date: Sat, 16 Nov 2013 12:01:47 +0530 [thread overview]
Message-ID: <20131116063147.GH8834@intel.com> (raw)
In-Reply-To: <20131115125604.a12f24a58bcbf91cc26cc20e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 1918 bytes --]
On Fri, Nov 15, 2013 at 12:56:04PM +1100, Stephen Rothwell wrote:
> Hi Dan,
>
> Today's linux-next merge of the dmaengine tree got a conflict in
> drivers/dma/dmatest.c between commit 19e9f99f273b ("dmaengine: dmatest:
> use DMA_COMPLETE for dma completion status") from the slave-dma tree and
> commit 872f05c6e9a3 ("dmatest: replace stored results mechanism, with
> uniform messages") from the dmaengine tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no action
> is required).
Thanks, we are sending single PULL to linus so I am merging Dan's tree to mine
so this should vanish
--
~Vinod
>
> --
> Cheers,
> Stephen Rothwell sfr@canb.auug.org.au
>
> diff --cc drivers/dma/dmatest.c
> index 59e287f56dfc,329b7cf02f8e..000000000000
> --- a/drivers/dma/dmatest.c
> +++ b/drivers/dma/dmatest.c
> @@@ -735,17 -633,17 +633,17 @@@ static int dmatest_func(void *data
> * free it this time?" dancing. For now, just
> * leave it dangling.
> */
> - thread_result_add(info, result, DMATEST_ET_TIMEOUT,
> - total_tests, src_off, dst_off,
> - len, 0);
> + dmaengine_unmap_put(um);
> + result("test timed out", total_tests, src_off, dst_off,
> + len, 0);
> failed_tests++;
> continue;
> - } else if (status != DMA_SUCCESS) {
> + } else if (status != DMA_COMPLETE) {
> - enum dmatest_error_type type = (status == DMA_ERROR) ?
> - DMATEST_ET_DMA_ERROR : DMATEST_ET_DMA_IN_PROGRESS;
> - thread_result_add(info, result, type,
> - total_tests, src_off, dst_off,
> - len, status);
> + dmaengine_unmap_put(um);
> + result(status == DMA_ERROR ?
> + "completion error status" :
> + "completion busy status", total_tests, src_off,
> + dst_off, len, ret);
> failed_tests++;
> continue;
> }
--
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-11-16 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 1:56 linux-next: manual merge of the dmaengine tree with the slave-dma tree Stephen Rothwell
2013-11-16 6:31 ` Vinod Koul [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-09-10 1:56 Stephen Rothwell
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=20131116063147.GH8834@intel.com \
--to=vinod.koul@intel.com \
--cc=dan.j.williams@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.