linux-renesas-soc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-renesas-soc@vger.kernel.org" 
	<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH v2 0/3] dmaengine: rcar-dmac: use of_data and add dma-channel-mask support
Date: Wed, 4 Sep 2019 10:08:02 +0000	[thread overview]
Message-ID: <TYAPR01MB4544C3A8C8F3E5559E903A2ED8B80@TYAPR01MB4544.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20190904093629.GS2672@vkoul-mobl>

Hi Vinod,

> From: Vinod Koul, Sent: Wednesday, September 4, 2019 6:36 PM
> 
> On 04-09-19, 17:24, Yoshihiro Shimoda wrote:
> > This patch series is based on the latest slave-dma.git / next branch and
> > merge the latest slave-dma.git / fixes branch. This is because this patch
> > series depends on the following commit:
> 
> Well it should not depend on fix which is going for 5.3 and the rest for
> 5.4
> 
> Can you please rebase on next and send. This doesnt apply for me

I'm sorry for bothering you. I have a question. The patch 1/3 [1] and 3/3 [2]
completely depends on the fix patch [3] because the fix patch added
a new member and the patch 3/3 used it. How do I handle such a case?
Should I wait for submitting this patch series until v5.3 is released?
# If so, I think this means this patch series will be merged into v5.5.

[1] https://patchwork.kernel.org/patch/11129607/
[2] https://patchwork.kernel.org/patch/11129601/
[3]
https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/slave-dma.git/commit/?h=fixes&id=cf24aac38698bfa1d021afd3883df3c4c65143a4

Best regards,
Yoshihiro Shimoda

> Thanks
> 
> > ---
> > commit cf24aac38698bfa1d021afd3883df3c4c65143a4
> > Author: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> > Date:   Mon Sep 2 20:44:03 2019 +0900
> >
> >     dmaengine: rcar-dmac: Fix DMACHCLR handling if iommu is mapped
> > ---
> >
> > Changes from v1:
> >  - Combine two patch series into this patch series.
> > https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=166457&state=*
> > https://patchwork.kernel.org/project/linux-renesas-soc/list/?series=166457&state=*
> >  - Remove a patch because updated patch is already merged into
> >    the latest slave-dma.git / fixes branch as described above.
> >  - Add Reviewed-by tags into all patches.
> >  - Rename a member of rcar_dmac_of_data.
> >  - Just ignore the return value of of_property_read_u32() for dma-channel-mask.
> >
> > Yoshihiro Shimoda (3):
> >   dmaengine: rcar-dmac: Use of_data values instead of a macro
> >   dmaengine: rcar-dmac: Use devm_platform_ioremap_resource()
> >   dmaengine: rcar-dmac: Add dma-channel-mask property support
> >
> >  drivers/dma/sh/rcar-dmac.c | 47 +++++++++++++++++++++++++++++++++++++---------
> >  1 file changed, 38 insertions(+), 9 deletions(-)
> >
> > --
> > 2.7.4
> 
> --
> ~Vinod

      reply	other threads:[~2019-09-04 10:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04  8:24 [PATCH v2 0/3] dmaengine: rcar-dmac: use of_data and add dma-channel-mask support Yoshihiro Shimoda
2019-09-04  8:24 ` [PATCH v2 1/3] dmaengine: rcar-dmac: Use of_data values instead of a macro Yoshihiro Shimoda
2019-09-04  8:24 ` [PATCH v2 2/3] dmaengine: rcar-dmac: Use devm_platform_ioremap_resource() Yoshihiro Shimoda
2019-09-04  8:24 ` [PATCH v2 3/3] dmaengine: rcar-dmac: Add dma-channel-mask property support Yoshihiro Shimoda
2019-09-04  9:36 ` [PATCH v2 0/3] dmaengine: rcar-dmac: use of_data and add dma-channel-mask support Vinod Koul
2019-09-04 10:08   ` Yoshihiro Shimoda [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=TYAPR01MB4544C3A8C8F3E5559E903A2ED8B80@TYAPR01MB4544.jpnprd01.prod.outlook.com \
    --to=yoshihiro.shimoda.uh@renesas.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=vkoul@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).