From: Appana Durga Kedareswara Rao <appana.durga.rao@xilinx.com>
To: "Koul, Vinod" <vinod.koul@intel.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Anirudha Sarangi" <anirudh@xilinx.com>,
Michal Simek <michals@xilinx.com>,
"Williams, Dan J" <dan.j.williams@intel.com>,
Soren Brinkmann <sorenb@xilinx.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"arnd@arndb.de" <arnd@arndb.de>
Subject: RE: [PATCH v6 2/2] dmaengine: Add Xilinx AXI Central Direct Memory Access Engine driver support
Date: Mon, 5 Oct 2015 14:19:55 +0000 [thread overview]
Message-ID: <C246CAC1457055469EF09E3A7AC4E11A4A4EC207@XAP-PVEXMBX01.xlnx.xilinx.com> (raw)
In-Reply-To: <1444054201.3579.22.camel@intel.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 1617 bytes --]
Hi Vinod,
> -----Original Message-----
> From: dmaengine-owner@vger.kernel.org [mailto:dmaengine-
> owner@vger.kernel.org] On Behalf Of Koul, Vinod
> Sent: Monday, October 05, 2015 7:40 PM
> To: Appana Durga Kedareswara Rao
> Cc: linux-kernel@vger.kernel.org; Anirudha Sarangi; Michal Simek; Williams, Dan
> J; Soren Brinkmann; dmaengine@vger.kernel.org; linux-arm-
> kernel@lists.infradead.org; arnd@arndb.de
> Subject: Re: [PATCH v6 2/2] dmaengine: Add Xilinx AXI Central Direct Memory
> Access Engine driver support
>
> On Mon, 2015-10-05 at 13:50 +0000, Appana Durga Kedareswara Rao wrote:
>
> > >
> > > On Mon, Sep 07, 2015 at 06:03:18PM +0530, Kedareswara rao Appana
> wrote:
> > > > This is the driver for the AXI Central Direct Memory Access (AXI
> > > > CDMA) core, which is a soft Xilinx IP core that provides
> > > > high-bandwidth Direct Memory Access (DMA) between a memory-mapped
> > > > source address and a memory-mapped destination address.
> > >
> > > Where is the 1/2 here ? I have only this one in my mails..
> >
> > You are there in the 1/2 not the dmaengine@vger.kernel.org.
>
> The threading is broken in your patch series. ON searching I found the 1/2.
> Please make sure patch series are threaded properly.
>
Sorry for the noise will take care from the next series onwards.
Regards,
Kedar.
> --
> ~Vinod
> N r y b X ǧv ^ )޺{.n + )ފ{ay \x1dʇڙ ,j f h z \x1e w j:+v w j m zZ+ ݢj" !
> i
ÿôèº{.nÇ+‰·Ÿ®‰†+%ŠËÿ±éݶ\x17¥Šwÿº{.nÇ+‰·¥Š{±þG«éÿŠ{ayº\x1dʇڙë,j\a¢f£¢·hšïêÿ‘êçz_è®\x03(階ŠÝ¢j"ú\x1a¶^[m§ÿÿ¾\a«þG«éÿ¢¸?™¨èÚ&£ø§~á¶iO•æ¬z·švØ^\x14\x04\x1a¶^[m§ÿÿÃ\fÿ¶ìÿ¢¸?–I¥
next prev parent reply other threads:[~2015-10-05 14:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 12:33 [PATCH v6 2/2] dmaengine: Add Xilinx AXI Central Direct Memory Access Engine driver support Kedareswara rao Appana
2015-10-05 13:39 ` Vinod Koul
2015-10-05 13:50 ` Appana Durga Kedareswara Rao
2015-10-05 14:10 ` Koul, Vinod
2015-10-05 14:19 ` Appana Durga Kedareswara Rao [this message]
2015-10-05 15:18 ` 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=C246CAC1457055469EF09E3A7AC4E11A4A4EC207@XAP-PVEXMBX01.xlnx.xilinx.com \
--to=appana.durga.rao@xilinx.com \
--cc=anirudh@xilinx.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michals@xilinx.com \
--cc=sorenb@xilinx.com \
--cc=vinod.koul@intel.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).