linux-kernel - Re: [PATCH v4 02/58] serial: at91: Use dmaengine_slave

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:	Mon, 3 Nov 2014 18:46:34 +0100
From:	Nicolas Ferre <nicolas.ferre@...el.com>
To:	Maxime Ripard <maxime.ripard@...e-electrons.com>
CC:	Vinod Koul <vinod.koul@...el.com>, <dmaengine@...r.kernel.org>,
	<lars@...afoo.de>, Russell King <linux@....linux.org.uk>,
	<linux-kernel@...r.kernel.org>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	<linux-arm-kernel@...ts.infradead.org>,
	Antoine Ténart <antoine@...e-electrons.com>
Subject: Re: [PATCH v4 02/58] serial: at91: Use dmaengine_slave_config API

On 03/11/2014 13:33, Maxime Ripard :
> Hi Nicolas,
> 
> On Mon, Nov 03, 2014 at 12:12:44PM +0100, Nicolas Ferre wrote:
>> On 28/10/2014 22:25, Maxime Ripard :
>>> We are removing the dmaengine_device_control API, that shouldn't even have been
>>> exposed in the first place. Change the callers to use the proper API.
>>>
>>> Signed-off-by: Maxime Ripard <maxime.ripard@...e-electrons.com>
>>
>> Acked-by: Nicolas Ferre <nicolas.ferre@...el.com>
>>
>> Thanks, Maxime. Do I have to carry the patch myself or is it part of a
>> series?
> 
> I think it would be better to keep it together with that serie, since
> we're removing dmaengine_device_control in a latter patch. If it's ok
> for you of course.

Fair enough, keep it in.

Thanks Maxime, bye,
-- 
Nicolas Ferre
--
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/