Message ID | 20220219005221.634-12-bhe@redhat.com (mailing list archive) |
---|---|
State | Not Applicable |
Delegated to: | Herbert Xu |
Headers | show |
Series | Don't use kmalloc() with GFP_DMA | expand |
> --- a/drivers/staging/media/imx/imx-media-utils.c
$subject says 'emxx_udc' instead of 'imx: media-utils'.
On Sat, Feb 19, 2022 at 08:52:10AM +0800, Baoquan He wrote: > dma_alloc_coherent() allocates dma buffer with device's addressing > limitation in mind. It's redundent to specify GFP_DMA when calling > dma_alloc_coherent(). Looks good: Reviewed-by: Christoph Hellwig <hch@lst.de>
On 02/19/22 at 07:51am, Wolfram Sang wrote: > > > --- a/drivers/staging/media/imx/imx-media-utils.c > > $subject says 'emxx_udc' instead of 'imx: media-utils'. Ah, good catch. It should be wrongly copied from the patch 12, will fix it, thanks.
diff --git a/drivers/staging/media/imx/imx-media-utils.c b/drivers/staging/media/imx/imx-media-utils.c index 94bc866ca28c..043281ec2e9d 100644 --- a/drivers/staging/media/imx/imx-media-utils.c +++ b/drivers/staging/media/imx/imx-media-utils.c @@ -588,7 +588,7 @@ int imx_media_alloc_dma_buf(struct device *dev, buf->len = PAGE_ALIGN(size); buf->virt = dma_alloc_coherent(dev, buf->len, &buf->phys, - GFP_DMA | GFP_KERNEL); + GFP_KERNEL); if (!buf->virt) { dev_err(dev, "%s: failed\n", __func__); return -ENOMEM;