linux-kernel - Re: [PATCH 0/7 v2] dma: sh: stop using .private

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]

Message-ID: <1342764028.1726.195.camel@vkoul-udesk3>
Date:	Fri, 20 Jul 2012 11:30:28 +0530
From:	Vinod Koul <vinod.koul@...ux.intel.com>
To:	Guennadi Liakhovetski <g.liakhovetski@....de>
Cc:	Magnus Damm <magnus.damm@...il.com>, linux-sh@...r.kernel.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/7 v2] dma: sh: stop using .private

On Thu, 2012-07-05 at 12:29 +0200, Guennadi Liakhovetski wrote:
> This patch series supersedes the one from yesterday with the same title. 
> The 4 patches from v1 are all unchanged, v2 just prepends them with 3 more 
> preparatory patches. From the original series description:
> 
> Here's an attempt to convert the shdma driver to a new method, whereby a 
> centrally provided filter function is used and the DMA_SLAVE_CONFIG command 
> is enabled for slave operation. The last patch is an illustration of how 
> this new method shall be used. If this approach is acceptable, I'll also 
> convert the remaining shdma user drivers. This patch series goes on top of 
> my earlier patches to split shdma.c.
Applied thanks.

Fixed one checkpatch issue though!!

ERROR: "(foo*)" should be "(foo *)"
#996: FILE: drivers/dma/sh/shdma-base.c:662:
+		config = (struct dma_slave_config*)arg;

Please *always* run checkpatch on the patches you send

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