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]
Message-ID: <50526DB8.3090808@wwwdotorg.org>
Date:	Thu, 13 Sep 2012 17:35:20 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Laxman Dewangan <ldewangan@...dia.com>
CC:	olof@...om.net, grant.likely@...retlab.ca, lrg@...com,
	broonie@...nsource.wolfsonmicro.com, vinod.koul@...ux.intel.com,
	linux@....linux.org.uk, linux-kernel@...r.kernel.org,
	linux-tegra@...r.kernel.org,
	spi-devel-general@...ts.sourceforge.net,
	alsa-devel@...a-project.org
Subject: Re: [PATCH 0/5] ARM: tegra: move all APB DMA client to dmaengine
 based driver

On 08/16/2012 08:13 AM, Laxman Dewangan wrote:
> This patch series enable the dmaengine based Tegra APB DMA driver
> and remove the support code for the legacy dma driver from different
> APB DMA clients.
> Patch 1 enable the dmaengine based dma drie and disable the legacy dma driver
>         in config file.
> Patch 2 remove the legacy dma driver.
> Patch 3,4, 5 remove the support code from different APB DMA clients to support
>         legacy dma driver.
> 
> Please note that this series will depends on patch
> dma: tegra: enable/disable dma clock
> which is not in 3.6-rc1 but will be available in next RC (rc2) of 3.6 as
> part of fixes.

I have applied this series to Tegra's for-3.7/dmaengine branch. Right
now, that branch is based directly on Mark Brown's ASoC for-3.6 branch
in order to pick up the fix it depends on. However, I'll rebase on the
3.6 pull request tag he sends for that branch as soon as it's available.
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ