dmaengine.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: yibin.gong@nxp.com
Cc: robh@kernel.org, shawnguo@kernel.org, s.hauer@pengutronix.de,
	festevam@gmail.com, mark.rutland@arm.com,
	dan.j.williams@intel.com, angelo@sysam.it, linux-imx@nxp.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org,
	devicetree@vger.kernel.org, kernel@pengutronix.de
Subject: Re: [PATCH v4 1/6] dmaengine: fsl-edma: add drvdata for fsl-edma
Date: Tue, 25 Jun 2019 09:42:16 +0530	[thread overview]
Message-ID: <20190625041216.GE2962@vkoul-mobl> (raw)
In-Reply-To: <20190614081724.13366-2-yibin.gong@nxp.com>

On 14-06-19, 16:17, yibin.gong@nxp.com wrote:
> From: Robin Gong <yibin.gong@nxp.com>
> 
> There are some differences between vf610 and next i.mx7ulp. Put such
> differences into static driver data for distiguish easily at driver

Typo distiguish 

Though I tried to apply 1-5 it doesnt apply for me, can you rebase and
resend

Thanks

-- 
~Vinod

  reply	other threads:[~2019-06-25  4:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-14  8:17 [PATCH v4 0/6] add edma2 for i.mx7ulp yibin.gong
2019-06-14  8:17 ` [PATCH v4 1/6] dmaengine: fsl-edma: add drvdata for fsl-edma yibin.gong
2019-06-25  4:12   ` Vinod Koul [this message]
2019-06-25  7:08     ` Robin Gong
2019-06-14  8:17 ` [PATCH v4 2/6] dmaengine: fsl-edma-common: move dmamux register to another single function yibin.gong
2019-06-14  8:17 ` [PATCH v4 3/6] dmaengine: fsl-edma-common: version check for v2 instead yibin.gong
2019-06-14  8:17 ` [PATCH v4 4/6] dt-bindings: dma: fsl-edma: add new i.mx7ulp-edma yibin.gong
2019-06-14  8:17 ` [PATCH v4 5/6] dmaengine: fsl-edma: add i.mx7ulp edma2 version support yibin.gong
2019-06-14  8:17 ` [PATCH v4 6/6] ARM: dts: imx7ulp: add edma device node yibin.gong

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=20190625041216.GE2962@vkoul-mobl \
    --to=vkoul@kernel.org \
    --cc=angelo@sysam.it \
    --cc=dan.j.williams@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=yibin.gong@nxp.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).