public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Prarit Bhargava <prarit@redhat.com>
To: Nicholas Mc Guire <der.herr@hofr.at>
Cc: Dan Williams <dan.j.williams@intel.com>,
	Vinod Koul <vinod.koul@intel.com>,
	dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] incorrect use of init_completion fixup
Date: Wed, 24 Dec 2014 14:01:57 -0500	[thread overview]
Message-ID: <549B0DA5.3010700@redhat.com> (raw)
In-Reply-To: <1419357151-22889-1-git-send-email-der.herr@hofr.at>



On 12/23/2014 12:52 PM, Nicholas Mc Guire wrote:
> The successive init_completion calls should be reinit_completion here.
> 

Hi Nicholas,

I know enough about this code to break it ;) ... what condition did you hit that
led you to this patch?

P.

> patch is against 3.18.0 linux-next
> 
> Signed-off-by: Nicholas Mc Guire <der.herr@hofr.at>
> ---
>  drivers/dma/ioat/dma_v3.c |    4 +-
>  1 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/dma/ioat/dma_v3.c b/drivers/dma/ioat/dma_v3.c
> index 32eae38..3dbcc42 100644
> --- a/drivers/dma/ioat/dma_v3.c
> +++ b/drivers/dma/ioat/dma_v3.c
> @@ -1353,7 +1353,7 @@ static int ioat_xor_val_self_test(struct ioatdma_device *device)
>  	}
> 
>  	async_tx_ack(tx);
> -	init_completion(&cmp);
> +	reinit_completion(&cmp);
>  	tx->callback = ioat3_dma_test_callback;
>  	tx->callback_param = &cmp;
>  	cookie = tx->tx_submit(tx);
> @@ -1405,7 +1405,7 @@ static int ioat_xor_val_self_test(struct ioatdma_device *device)
>  	}
> 
>  	async_tx_ack(tx);
> -	init_completion(&cmp);
> +	reinit_completion(&cmp);
>  	tx->callback = ioat3_dma_test_callback;
>  	tx->callback_param = &cmp;
>  	cookie = tx->tx_submit(tx);
> --
> 1.7.10.4
> 

  reply	other threads:[~2014-12-24 19:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-23 17:52 [PATCH] incorrect use of init_completion fixup Nicholas Mc Guire
2014-12-24 19:01 ` Prarit Bhargava [this message]
2014-12-24 19:11   ` Nicholas Mc Guire
     [not found] <49ea5f8dc52545d4a5df6b1ad8302410@HT17-E6.exg6.exghost.com>
2014-12-24  2:14 ` Ed Cashin
  -- strict thread matches above, loose matches on Subject: below --
2014-12-23 17:44 Nicholas Mc Guire

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=549B0DA5.3010700@redhat.com \
    --to=prarit@redhat.com \
    --cc=dan.j.williams@intel.com \
    --cc=der.herr@hofr.at \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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