linux-kernel - Re: [PATCH 0/3] dmaengine: at

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:	Tue, 15 May 2012 08:48:34 +0530
From:	Vinod Koul <vinod.koul@...ux.intel.com>
To:	Nicolas Ferre <nicolas.ferre@...el.com>
Cc:	linux-arm-kernel@...ts.infradead.org, plagnioj@...osoft.com,
	linux-kernel@...r.kernel.org, ludovic.desroches@...el.com
Subject: Re: [PATCH 0/3] dmaengine: at_hdmac: slave configuration

On Thu, 2012-05-10 at 12:17 +0200, Nicolas Ferre wrote:
> This patch series is composed of two cleanup patches and one "slave
> configuration" patch. The last one uses configuration data passed through the
> slave configuration API to setup the DMA controller.
> Corresponding custom configuration is removed from the slave DMA private
> structure and its use in the AT91 files. Header definitions are then moved
> accordingly.
> 
> Nicolas Ferre (3):
>   dmaengine: at_hdmac: remove some at_dma_slave comments
>   dmaengine: at_hdmac: remove ATC_DEFAULT_CTRLA constant
>   dmaengine: at_hdmac: take maxburst from slave configuration
> 
>  arch/arm/mach-at91/at91sam9g45_devices.c   |    1 -
>  arch/arm/mach-at91/include/mach/at_hdmac.h |   26 --------------------------
>  drivers/dma/at_hdmac.c                     |   15 +++++++--------
>  drivers/dma/at_hdmac_regs.h                |   21 ++++++++++++++++++++-
>  4 files changed, 27 insertions(+), 36 deletions(-)
Applied, Thanks


-- 
~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/