Hi Robin, >-----Original Message----- >From: Robin Murphy [mailto:robin.murphy@xxxxxxx] >Sent: Wednesday, October 26, 2016 8:37 PM >To: Sricharan R <sricharan@xxxxxxxxxxxxxx>; will.deacon@xxxxxxx; joro@xxxxxxxxxx; iommu@xxxxxxxxxxxxxxxxxxxxxxxxxx; linux-arm- >kernel@xxxxxxxxxxxxxxxxxxx; linux-arm-msm@xxxxxxxxxxxxxxx; laurent.pinchart@xxxxxxxxxxxxxxxx; m.szyprowski@xxxxxxxxxxx; >tfiga@xxxxxxxxxxxx; srinivas.kandagatla@xxxxxxxxxx >Subject: Re: [PATCH V3 6/8] arm: dma-mapping: Reset the device's dma_ops > >On 04/10/16 18:03, Sricharan R wrote: >> The dma_ops for the device is not getting set to NULL in >> arch_tear_down_dma_ops and this causes an issue when the >> device's probe gets deferred and retried. So reset the >> dma_ops to NULL. > >Reviewed-by: Robin Murphy <robin.murphy@xxxxxxx> > Thanks. >This seems like it could stand independently from the rest of the series >- might be worth rewording the commit message to more general terms, >i.e. arch_teardown_dma_ops() being the inverse of arch_setup_dma_ops() >thus clearing the ops set by the latter, and sending it to Russell as a >fix in its own right. Ok, will reword the commit log and push this separately. Regards, Sricharan -- To unsubscribe from this list: send the line "unsubscribe linux-arm-msm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
