[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190201161116.GG6532@lst.de>
Date: Fri, 1 Feb 2019 17:11:16 +0100
From: Christoph Hellwig <hch@....de>
To: Robin Murphy <robin.murphy@....com>
Cc: Christoph Hellwig <hch@....de>, John Crispin <john@...ozen.org>,
Vinod Koul <vkoul@...nel.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 10/18] smc911x: pass struct device to DMA API functions
On Fri, Feb 01, 2019 at 02:14:34PM +0000, Robin Murphy wrote:
> And equivalently for rxdma here. However, given that this all seems only
> relevant to antique ARCH_PXA platforms which are presumably managing to
> work as-is, it's probably not worth tinkering too much. I'd just stick a
> note in the commit message that we're still only making these
> self-consistent with the existing dma_map_single() calls rather than
> necessarily correct.
Sounds good.
Powered by blists - more mailing lists