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
| ||
|
Message-ID: <20190202101121.GE4296@vkoul-mobl> Date: Sat, 2 Feb 2019 15:41:21 +0530 From: Vinod Koul <vkoul@...nel.org> To: Christoph Hellwig <hch@....de> Cc: John Crispin <john@...ozen.org>, Dmitry Tarnyagin <dmitry.tarnyagin@...kless.no>, Nicolas Ferre <nicolas.ferre@...rochip.com>, Sudip Mukherjee <sudipm.mukherjee@...il.com>, Felipe Balbi <balbi@...nel.org>, linux-mips@...r.kernel.org, linux-kernel@...r.kernel.org, dmaengine@...r.kernel.org, netdev@...r.kernel.org, linux-usb@...r.kernel.org, linux-fbdev@...r.kernel.org, alsa-devel@...a-project.org, iommu@...ts.linux-foundation.org Subject: Re: [PATCH 02/18] dmaengine: imx-sdma: pass struct device to DMA API functions On 01-02-19, 09:47, Christoph Hellwig wrote: > The DMA API generally relies on a struct device to work properly, and > only barely works without one for legacy reasons. Pass the easily > available struct device from the platform_device to remedy this. This looks good to me but fails to apply. Can you please base it on dmaengine-next or linux-next please and resend Thanks -- ~Vinod
Powered by blists - more mailing lists