linux-kernel - Re: [PATCHv5] DMAEngine: Define interleaved transfer request api

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1318767386.23438.93.camel@vkoul-udesk3>
Date:	Sun, 16 Oct 2011 17:46:26 +0530
From:	Vinod Koul <vinod.koul@...el.com>
To:	Jassi Brar <jaswinder.singh@...aro.org>
Cc:	linux-kernel@...r.kernel.org, dan.j.williams@...el.com,
	rmk@....linux.org.uk, 21cnbao@...il.com
Subject: Re: [PATCHv5] DMAEngine: Define interleaved transfer request api

On Sun, 2011-10-16 at 16:46 +0530, Jassi Brar wrote:
> > IMO this looks decent now, we can take this for merge if we don't
> have
> > any other issues.
> > Ideally would be great if we also need to see the usage for this
> > API .... Barry?. I am okay to host this up on a branch meanwhile.
> >
> > Just a minor nitpick, I would have really like dmaxfer_template to be
> > named dma_interleaved_template. I think we are still quite far from
> > generic transfer template. Jassi if you agree I can fix that up while
> > applying, no need to revise for nitpick :)
> >
> There is need to provide cyclic functionality but we seem to disagree on
> implementation. So you might as well take this patch and provide
> cyclic feature, the way you want, as a patch on top of this.
> I am ok with dmaxfer_template renaming. 
Thanks, I have changed it and pushed to branch interleaved_dma.

Once Barry sends his drivers using this API, will merge 

-- 
~Vinod

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/