All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robherring2-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Andy Shevchenko
	<andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>,
	Vinod Koul <vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org
Subject: Re: [PATCH] of: dma: protect list write operation by spin_lock
Date: Mon, 28 Jan 2013 09:52:00 -0600	[thread overview]
Message-ID: <51069EA0.4040004@gmail.com> (raw)
In-Reply-To: <1359386694-20548-1-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>

On 01/28/2013 09:24 AM, Andy Shevchenko wrote:
> Signed-off-by: Andy Shevchenko <andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
> ---
>  drivers/of/dma.c |    2 ++
>  1 file changed, 2 insertions(+)

You need to cc whomever has this file in their tree which is Vinod.

Acked-by: Rob Herring <rob.herring-bsGFqQB8/DxBDgjK7y7TUQ@public.gmane.org>

Vinod, it's probably better to move drivers/of/dma.c to drivers/dma.
That's been the direction we've been taking with new OF binding code. I
must have missed that in the review.

Rob

> 
> diff --git a/drivers/of/dma.c b/drivers/of/dma.c
> index 59631b2..1ae6120 100644
> --- a/drivers/of/dma.c
> +++ b/drivers/of/dma.c
> @@ -117,7 +117,9 @@ int of_dma_controller_register(struct device_node *np,
>  	ofdma->use_count = 0;
>  
>  	/* Now queue of_dma controller structure in list */
> +	spin_lock(&of_dma_lock);
>  	list_add_tail(&ofdma->of_dma_controllers, &of_dma_list);
> +	spin_unlock(&of_dma_lock);
>  
>  	return 0;
>  }
> 

  parent reply	other threads:[~2013-01-28 15:52 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-28 15:24 [PATCH] of: dma: protect list write operation by spin_lock Andy Shevchenko
     [not found] ` <1359386694-20548-1-git-send-email-andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
2013-01-28 15:52   ` Rob Herring [this message]
     [not found]     ` <51069EA0.4040004-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-01-28 16:07       ` Vinod Koul
     [not found]         ` <20130128160757.GA6396-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-01-29 15:36           ` Rob Herring
     [not found]             ` <5107EC8D.5070001-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-02-12 17:20               ` Vinod Koul
     [not found]                 ` <20130212172027.GT3789-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2013-02-13  7:48                   ` Andy Shevchenko
2013-02-13 10:48                     ` Vinod Koul

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=51069EA0.4040004@gmail.com \
    --to=robherring2-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=andriy.shevchenko-VuQAYsv1563Yd54FQh9/CA@public.gmane.org \
    --cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
    --cc=vinod.koul-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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 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.