From: Simon Horman <horms@verge.net.au>
To: linux-sh@vger.kernel.org
Subject: [off-list] Re: [PATCH 0/3] rcar-hpbdma: fixup patches for double plane
Date: Tue, 29 Oct 2013 05:11:22 +0000 [thread overview]
Message-ID: <20131029051121.GH20432@verge.net.au> (raw)
In-Reply-To: <87k3hc189h.wl%kuninori.morimoto.gx@renesas.com>
Hi Morimoto-san,
as these are dma patches shouldn't they go through (lazy) Vinod?
If so, I'll Ack them ask you to repost them on the ML.
If not, I guess I can set up a branch and see if I can get
them accepted through the arm-soc tree or elsewhere.
On Thu, Oct 17, 2013 at 05:03:54PM -0700, Kuninori Morimoto wrote:
>
> Hi Simon
>
> These are v2 of R-Car HBPDMA fixup patches
> for double plane.
>
> Kuninori Morimoto (3):
> rcar-hpbdma: add max transfer size
> rcar-hpbdma: initialise plane information when halted
> rcar-hpbdma: fixup channel busy check for double plane
>
> drivers/dma/sh/rcar-hpbdma.c | 10 +++++++++-
> 1 file changed, 9 insertions(+), 1 deletion(-)
>
> Best regards
> ---
> Kuninori Morimoto
> --
> To unsubscribe from this list: send the line "unsubscribe linux-sh" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
next prev parent reply other threads:[~2013-10-29 5:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-17 10:50 [PATCH 0/3] rcar-hpbdma: fixup patches for double plane Kuninori Morimoto
2013-10-17 12:39 ` Max Filippov
2013-10-18 0:03 ` Kuninori Morimoto
2013-10-29 5:11 ` Simon Horman [this message]
2013-10-29 5:12 ` Simon Horman
2013-10-29 6:51 ` Kuninori Morimoto
2013-10-29 6:52 ` [PATCH 1/3] rcar-hpbdma: add max transfer size Kuninori Morimoto
2013-10-29 6:52 ` [PATCH 2/3] rcar-hpbdma: initialise plane information when halted Kuninori Morimoto
2013-10-29 6:52 ` [PATCH 3/3] rcar-hpbdma: fixup channel busy check for double plane Kuninori Morimoto
2013-10-29 7:08 ` [PATCH 0/3] rcar-hpbdma: fixup patches " Simon Horman
2013-11-12 2:16 ` Kuninori Morimoto
2013-11-12 5:03 ` 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=20131029051121.GH20432@verge.net.au \
--to=horms@verge.net.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).