linux-kernel - Re: [PATCH 0/9] ARM: tegra: move to generic DMA DT binding

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] [day] [month] [year] [list]

Date:	Fri, 26 Jul 2013 13:25:20 -0600
From:	Stephen Warren <swarren@...dotorg.org>
To:	Richard Zhao <rizhao@...dia.com>
CC:	devicetree-discuss@...ts.ozlabs.org, linux-doc@...r.kernel.org,
	linux-tegra@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org, linux-spi@...r.kernel.org,
	linux-serial@...r.kernel.org, alsa-devel@...a-project.org,
	grant.likely@...aro.org, rob.herring@...xeda.com, rob@...dley.net,
	vinod.koul@...el.com, djbw@...com, broonie@...nel.org,
	gregkh@...uxfoundation.org, lgirdwood@...il.com,
	linuxzsc@...il.com, ldewangan@...dia.com, dev@...xeye.de
Subject: Re: [PATCH 0/9] ARM: tegra: move to generic DMA DT binding

On 07/23/2013 10:09 PM, Richard Zhao wrote:
> The patch series aim to move apbdma to generic DT binding.
> 
> Changes:
> - It add dmas/dma-names properties while leave
>   nvidia,dma-request-selector to be compatible.
> - update apbdma driver and dma client drivers
> - ASoC tegra adds a new struct to pass device and dma-name.
> - at last, remove legacy nvidia,dma-request-selector

I would like to take this series through the Tegra tree to simplify
dependencies. So, I'm looking for ack's on the drivers rather than for
them to be applied. I had hoped Richard would point this out when
posting the patches.
--
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/