All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vinod Koul <vinod.koul@intel.com>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 0/2] dmaengine: shdmac/rcar-hpbdma: fixup WARNING of slave caps retrieval
Date: Mon, 26 Jan 2015 06:32:24 +0000	[thread overview]
Message-ID: <20150126063224.GH28763@intel.com> (raw)
In-Reply-To: <878ugvmtoa.wl%kuninori.morimoto.gx@renesas.com>

On Thu, Jan 22, 2015 at 02:31:42AM +0000, Kuninori Morimoto wrote:
> 
> Vi Vinod
> 
> I had sent rcar-hpbdma directions fixup patches before
> 
> 	Subject: [PATCH v3] dmaengine:: rcar-hpbdma: add dma_dev->directions
> 	Date: Tue, 20 Jan 2015 01:22:48 +0000
> 
> After that, I got feedback from Laurent about residue_granularity.
> But, then, I could find above patch on dma/next branch, so, I sent below
> patch as additional patch.
> 
> 	Subject: [PATCH] dmaengine: rcar-hpbdma: tidyup residue_granularity
> 	Date: Wed, 21 Jan 2015 04:42:22 +0000
> 
> But, could you please replace it to 1) if possible ?
> I found shdmac has same issue (= 2).
I will just apply this patch, so should be okay..

-- 
~Vinod

> 
> Kuninori Morimoto (2):
>       1) dmaengine: rcar-hpbdma: fixup WARNING of slave caps retrieval
>       2) dmaengine: shdmac: fixup WARNING of slave caps retrieval
> 
>  drivers/dma/sh/rcar-hpbdma.c |    6 ++++++
>  drivers/dma/sh/shdmac.c      |    9 +++++++++
>  2 files changed, 15 insertions(+)
> 
> --
> To unsubscribe from this list: send the line "unsubscribe dmaengine" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

-- 

  parent reply	other threads:[~2015-01-26  6:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-22  2:31 [PATCH 0/2] dmaengine: shdmac/rcar-hpbdma: fixup WARNING of slave caps retrieval Kuninori Morimoto
2015-01-22 11:33 ` Laurent Pinchart
2015-01-26  6:32 ` Vinod Koul [this message]
2015-01-26  6:39 ` 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=20150126063224.GH28763@intel.com \
    --to=vinod.koul@intel.com \
    --cc=linux-sh@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 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.