From: Vinod Koul <vkoul@kernel.org>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: vinod.koul@intel.com, dmaengine@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v3 0/4] dmaengine: rcar-dmac: use of_data and add dma-channel-mask support
Date: Mon, 14 Oct 2019 12:28:02 +0530 [thread overview]
Message-ID: <20191014065802.GA2654@vkoul-mobl> (raw)
In-Reply-To: <1568010892-17606-1-git-send-email-yoshihiro.shimoda.uh@renesas.com>
On 09-09-19, 15:34, Yoshihiro Shimoda wrote:
> This patch series is based on the latest slave-dma.git / next branch.
>
> Changes from v2:
> - Rebase the latest slave-dma.git / next branch (In other words,
> this patch series doesn't depend any other branches.
> - Cherry-picked a patch which is contained in v5.3-rc8 to solve any
> dependency. (I'm not sure whether this is a right way or not...)
> https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=169317
Sorry for delay, I was on vacation + conference. Yeah ideally I would
merge fixes and this wouldn't be the case.
patch1 is no longer needed now, I have applied the rest
Thanks
--
~Vinod
prev parent reply other threads:[~2019-10-14 6:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-09 6:34 [PATCH v3 0/4] dmaengine: rcar-dmac: use of_data and add dma-channel-mask support Yoshihiro Shimoda
2019-09-09 6:34 ` [PATCH v3 1/4] dmaengine: rcar-dmac: Fix DMACHCLR handling if iommu is mapped Yoshihiro Shimoda
2019-09-09 6:34 ` [PATCH v3 2/4] dmaengine: rcar-dmac: Use of_data values instead of a macro Yoshihiro Shimoda
2019-09-13 8:48 ` Simon Horman
2019-09-09 6:34 ` [PATCH v3 3/4] dmaengine: rcar-dmac: Use devm_platform_ioremap_resource() Yoshihiro Shimoda
2019-09-13 8:46 ` Simon Horman
2019-09-09 6:34 ` [PATCH v3 4/4] dmaengine: rcar-dmac: Add dma-channel-mask property support Yoshihiro Shimoda
2019-10-14 6:58 ` 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=20191014065802.GA2654@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=vinod.koul@intel.com \
--cc=yoshihiro.shimoda.uh@renesas.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;
as well as URLs for NNTP newsgroup(s).