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: <2c542d87-3fd6-62db-1e37-159b673f6dc2@ti.com>
Date:	Mon, 18 Jul 2016 15:30:17 +0300
From:	Peter Ujfalusi <peter.ujfalusi@...com>
To:	Russell King - ARM Linux <linux@...linux.org.uk>
CC:	<vinod.koul@...el.com>, <linux-kernel@...r.kernel.org>,
	<dmaengine@...r.kernel.org>,
	<linux-arm-kernel@...ts.infradead.org>,
	<linux-omap@...r.kernel.org>, <tony@...mide.com>
Subject: Re: [PATCH 0/7] dmaengine:omap-dma: Linked List transfer for slave_sg

On 07/18/16 15:21, Russell King - ARM Linux wrote:
> On Mon, Jul 18, 2016 at 03:07:57PM +0300, Peter Ujfalusi wrote:
>> I was not aware of any position on this from TI - as I mentioned I was not
>> involved with DMA. It could be that the position from 'TI' is still what it
>> was. Or changed. But as I have been asked to look after TI DMA drivers
>> upstream and I believe that the linked list mode is a good thing to have -
>> which is backed by my experiences. My position is that linked list support is
>> cool.
> 
> That's really nice news.  Nothing like asking the author first whether
> he'd like to pass over maintainership of the driver.  I guess you won't
> mind if at some point in the future, I decide to just take it back...

I work with the DMA drivers on behalf of TI. Inside TI the DMA related queries
are targeted at me. This does not change the maintainer of the drivers upstream.

-- 
Péter

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ