From: Barry Song <Barry.Song@csr.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Jassi Brar <jaswinder.singh@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
DL-SHA-WorkGroupLinux <Workgroup.Linux@csr.com>,
Rongjun Ying <Rongjun.Ying@csr.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [PATCH v4] dmaengine: add CSR SiRFprimaII DMAC driver
Date: Fri, 28 Oct 2011 08:08:27 +0000 [thread overview]
Message-ID: <5EB3BFCD089AD643B9BB63439F5FD5E98419FAC0@SHAASIEXM01.ASIA.ROOT.PRI> (raw)
In-Reply-To: <1319774982.20054.228.camel@vkoul-udesk3>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset="utf-8", Size: 2843 bytes --]
> -----Original Message-----
> From: Barry Song
> Sent: 2011å¹´10æ28æ¥ 13:04
> To: 'Vinod Koul'
> Cc: Arnd Bergmann; Jassi Brar; Linus Walleij; linux-kernel@vger.kernel.org;
> DL-SHA-WorkGroupLinux; Rongjun Ying; linux-arm-kernel@lists.infradead.org
> Subject: RE: [PATCH v4] dmaengine: add CSR SiRFprimaII DMAC driver
>
> > -----Original Message-----
> > From: Vinod Koul [mailto:vinod.koul@intel.com]
> > Sent: 2011å¹´10æ28æ¥ 12:10
> > To: Barry Song
> > Cc: Arnd Bergmann; Jassi Brar; Linus Walleij; linux-kernel@vger.kernel.org;
> > DL-SHA-WorkGroupLinux; Rongjun Ying; linux-arm-kernel@lists.infradead.org
> > Subject: RE: [PATCH v4] dmaengine: add CSR SiRFprimaII DMAC driver
> >
> > On Fri, 2011-10-28 at 01:49 +0000, Barry Song wrote:
> > > > Also, Please ensure you send patches which compile with ZERO warnings:
> > > > drivers/dma/sirf-dma.c: In function 'sirfsoc_dma_probe':
> > > > drivers/dma/sirf-dma.c:616: warning: assignment from incompatible
> > pointer
> > > > type
> > > > drivers/dma/sirf-dma.c:617: warning: assignment from incompatible
> > pointer
> > > > type
> > > > which comes from the fact that your prep_interleaved_dma does not have
> > > > last argument of flags.
> > > > On the second one you have not rebased to patch from Jassi which I
> > > > applied after converting direction stuff.
> > >
> > >
> > [pls wrap 80chars within paragraphs, i have reformatted below)
> > > I rebased to both yours and Jassi by my merging manually. I remember
> > > you have changed the last param of device_prep_dma_cyclic from
> > > dma_data_direction to dma_transfer_direction. After checking the tree
> > > interleaved_dma @ git://git.infradead.org/users/vkoul/slave-dma.git,
> > > it doesn't. then make another compiling warning in
> > > sirfsoc_dma_prep_cyclic(). so I'll still use dma_data_direction in
> > > sirfsoc_dma_prep_cyclic().
> > Yes for cyclic, I have missed to fix that. I will push the fixed version
>
> Ok. note my v5 is still using dma_data_direction. You might take care too :-)
Vinod, as I have acked interleaved dma API explicitly before, could you pls add:
Acked-by: Barry Song <Baohua.Song@csr.com>
in the commit of " DMAEngine: Define interleaved transfer request api" in your tree too. I didn't find it after I fetch your tree :-)
>
> > now
> >
> > --
> > ~Vinod
-barry
Member of the CSR plc group of companies. CSR plc registered in England and Wales, registered number 4187346, registered office Churchill House, Cambridge Business Park, Cowley Road, Cambridge, CB4 0WZ, United Kingdom
More information can be found at www.csr.com. Follow CSR on Twitter at http://twitter.com/CSR_PLC and read our blog at www.csr.com/blog
ÿôèº{.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:[~2011-10-28 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 3:08 Barry Song
2011-10-27 8:18 ` Vinod Koul
2011-10-27 8:31 ` Barry Song
2011-10-27 8:33 ` Russell King - ARM Linux
2011-10-27 8:38 ` Vinod Koul
2011-10-28 1:49 ` Barry Song
2011-10-28 4:09 ` Vinod Koul
2011-10-28 5:03 ` Barry Song
2011-10-28 8:08 ` Barry Song [this message]
2011-10-29 14:07 ` 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=5EB3BFCD089AD643B9BB63439F5FD5E98419FAC0@SHAASIEXM01.ASIA.ROOT.PRI \
--to=barry.song@csr.com \
--cc=Rongjun.Ying@csr.com \
--cc=Workgroup.Linux@csr.com \
--cc=arnd@arndb.de \
--cc=jaswinder.singh@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®