linux-kernel - Re: [PATCH/RFC] DMA engine driver for Marvell XOR engine

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 26 Jun 2008 15:33:16 -0700
From:	"Dan Williams" <dan.j.williams@...el.com>
To:	"Nicolas Pitre" <nico@....org>
Cc:	"Maciej Sosnowski" <maciej.sosnowski@...el.com>,
	"Saeed Bishara" <saeed@...vell.com>,
	"Lennert Buytenhek" <buytenh@...tstofly.org>,
	"Russell King" <linux@....linux.org.uk>,
	lkml <linux-kernel@...r.kernel.org>,
	"Haavard Skinnemoen" <hskinnemoen@...el.com>
Subject: Re: [PATCH/RFC] DMA engine driver for Marvell XOR engine

On Mon, Jun 23, 2008 at 9:46 AM, Nicolas Pitre <nico@....org> wrote:
> Here is a driver for the DMA/XOR engine found on many ARM SoCs from
> Marvell, such as Orion and newly supported Kirkwood.  Could interested
> people (notably Maciej Sosnowski and Dan Williams who are listed as
> maintainers for the DMA generic offload subsystem) review this patch,
> and ultimately provide their ACK, so we could push this driver along
> with additional ARM patches that depend on this one through the ARM git
> tree.
>

Hi Nicolas,

With Haavard's recently posted changes there is more activity in the
dmaengine/async_tx space with implications to mv_xor.  What
difficulties arise if I carry mv_xor through async_tx.git instead of
letting it go though arm.git, i.e. what patches do you have that
depend on mv_xor?

Thanks,
Dan
--
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/