From: Vinod Koul <vkoul@kernel.org>
To: Peng Ma <peng.ma@nxp.com>
Cc: "dan.j.williams@intel.com" <dan.j.williams@intel.com>,
Leo Li <leoyang.li@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: Re: [EXT] Re: [V4 2/2] dmaengine: fsl-dpaa2-qdma: Add NXP dpaa2 qDMA controller driver for Layerscape SoCs
Date: Tue, 24 Sep 2019 12:34:46 -0700 [thread overview]
Message-ID: <20190924193446.GF3824@vkoul-mobl> (raw)
In-Reply-To: <VI1PR04MB443142772665BB29B909DFF4EDB10@VI1PR04MB4431.eurprd04.prod.outlook.com>
Hey Peng,
On 11-09-19, 02:01, Peng Ma wrote:
> Hi Vinod,
>
> I send those series patchs(V5) on June 25, 2019. I haven't received any comments yet. Their current state
> is "Not Applicable", so please let me know what I need to do next.
> Thanks very much for your comments.
>
> Patch link:
> https://patchwork.kernel.org/patch/11015035/
> https://patchwork.kernel.org/patch/11015033/
Am sorry this looks to have missed by me and my script updated the
status.
Can you please resend me after rc1 is out and I will review it and do
the needful
--
~Vinod
next prev parent reply other threads:[~2019-09-24 19:35 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-13 10:13 [V4 1/2] dmaengine: fsl-dpaa2-qdma: Add the DPDMAI(Data Path DMA Interface) support Peng Ma
2019-06-13 10:13 ` [V4 2/2] dmaengine: fsl-dpaa2-qdma: Add NXP dpaa2 qDMA controller driver for Layerscape SoCs Peng Ma
2019-06-24 16:45 ` Vinod Koul
2019-09-11 2:01 ` [EXT] " Peng Ma
2019-09-24 19:34 ` Vinod Koul [this message]
2019-09-25 2:27 ` Peng Ma
2019-09-25 16:34 ` Vinod Koul
2019-09-26 6:53 ` Peng Ma
2019-06-14 1:36 ` [V4 1/2] dmaengine: fsl-dpaa2-qdma: Add the DPDMAI(Data Path DMA Interface) support Peng Ma
2019-06-24 12:25 ` 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=20190924193446.GF3824@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.ma@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).