All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@linux.intel.com>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Russell King <linux@arm.linux.org.uk>,
	Viresh Kumar <viresh.kumar@st.com>,
	Srinidhi Kasagar <srinidhi.kasagar@stericsson.com>,
	Linus Walleij <linus.walleij@stericsson.com>,
	Shawn Guo <shawn.guo@linaro.org>,
	Javier Martin <javier.martin@vista-silicon.com>,
	Richard Zhao <richard.zhao@linaro.org>,
	Yong Wang <yong.y.wang@intel.com>,
	Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/3] dmaengine: Use sg_dma_address instead of sg_phys
Date: Fri, 11 May 2012 14:01:10 +0530	[thread overview]
Message-ID: <1336725070.15424.1833.camel@vkoul-udesk3> (raw)
In-Reply-To: <CACRpkdaZv0ufh1fh9kmeXu0cC9GFWNwyVT6bXJSSWsM3bGSqog@mail.gmail.com>

On Thu, 2012-04-26 at 23:28 +0200, Linus Walleij wrote:
> On Wed, Apr 25, 2012 at 8:50 PM, Lars-Peter Clausen <lars@metafoo.de> wrote:
> 
> > dmaengine drivers should always use sg_dma_address instead of sg_phys to get the
> > addresses for the transfer from a sg element.
> 
> All three patches look correct to me (cannot test right now though).
> Acked-by: Linus Walleij <linus.walleij@linaro.org>
Thanks applied all 3.

-- 
~Vinod


      reply	other threads:[~2012-05-11  8:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-25 18:50 [PATCH 1/3] dmaengine: Use sg_dma_address instead of sg_phys Lars-Peter Clausen
2012-04-25 18:50 ` [PATCH 2/3] dmaengine: Use dma_sg_len(sg) instead of sg->length Lars-Peter Clausen
2012-04-25 18:50 ` [PATCH 3/3] dmaengine: Fixup dmaengine_prep_slave_single() to be actually useful Lars-Peter Clausen
2012-04-25 18:51 ` [PATCH 1/3] dmaengine: Use sg_dma_address instead of sg_phys Russell King - ARM Linux
2012-04-26 21:28 ` Linus Walleij
2012-05-11  8:31   ` Vinod Koul [this message]

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=1336725070.15424.1833.camel@vkoul-udesk3 \
    --to=vinod.koul@linux.intel.com \
    --cc=javier.martin@vista-silicon.com \
    --cc=kuninori.morimoto.gx@renesas.com \
    --cc=lars@metafoo.de \
    --cc=linus.walleij@linaro.org \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=richard.zhao@linaro.org \
    --cc=shawn.guo@linaro.org \
    --cc=srinidhi.kasagar@stericsson.com \
    --cc=viresh.kumar@st.com \
    --cc=yong.y.wang@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 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.