On Tue, Oct 17, 2017 at 10:28:09AM +0200, Greg KH wrote:
> On Tue, Oct 17, 2017 at 10:17:01AM +0200, Christoph Hellwig wrote:
> > Looks fine:
> >
> > Reviewed-by: Christoph Hellwig
> >
> > Greg, do you want to take this or should I queue it up in the
> > dma-mapping tree?
>
> You can take it, t
On Tue, Oct 17, 2017 at 10:17:01AM +0200, Christoph Hellwig wrote:
> Looks fine:
>
> Reviewed-by: Christoph Hellwig
>
> Greg, do you want to take this or should I queue it up in the
> dma-mapping tree?
You can take it, thanks!
Acked-by: Greg Kroah-Hartman
Looks fine:
Reviewed-by: Christoph Hellwig
Greg, do you want to take this or should I queue it up in the
dma-mapping tree?
We do not want the common dma_configure() pathway to apply
indiscriminately to all devices, since there are plenty of buses which
do not have DMA capability, and if their child devices were used for
DMA API calls it would only be indicative of a driver bug. However,
there are a number of buses for
4 matches
Mail list logo