From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org,hch@lst.de,harry@kernel.org,hebaoquan@kylinos.cn,akpm@linux-foundation.org
Subject: [merged mm-stable] media-staging-imx-dont-use-gfp_dma-when-calling-dma_alloc_coherent.patch removed from -mm tree
Date: Sat, 24 Oct 2026 01:58:28 -0700 [thread overview]
Message-ID: <20261024085829.3D7DD1F01825@smtp.kernel.org> (raw)
The quilt patch titled
Subject: media: staging: imx: don't use GFP_DMA when calling dma_alloc_coherent()
has been removed from the -mm tree. Its filename was
media-staging-imx-dont-use-gfp_dma-when-calling-dma_alloc_coherent.patch
This patch was dropped because it was merged into the mm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Baoquan He <hebaoquan@kylinos.cn>
Subject: media: staging: imx: don't use GFP_DMA when calling dma_alloc_coherent()
Date: Thu, 3 Sep 2026 19:18:31 +0800
dma_alloc_coherent() allocates the DMA buffer with the device's addressing
limitation in mind; the DMA core picks the zone from the device's coherent
DMA mask and ignores GFP_DMA passed by the caller. Remove the redundant
GFP_DMA flag.
Link: https://lore.kernel.org/20260903111836.1777265-9-hebaoquan@kylinos.cn
Signed-off-by: Baoquan He <hebaoquan@kylinos.cn>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
Cc: Christoph Hellwig <hch@lst.de>
Cc: Harry Yoo <harry@kernel.org>
---
drivers/staging/media/imx/imx-media-utils.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/drivers/staging/media/imx/imx-media-utils.c~media-staging-imx-dont-use-gfp_dma-when-calling-dma_alloc_coherent
+++ a/drivers/staging/media/imx/imx-media-utils.c
@@ -588,7 +588,7 @@ int imx_media_alloc_dma_buf(struct devic
buf->len = PAGE_ALIGN(size);
buf->virt = dma_alloc_coherent(dev, buf->len, &buf->phys,
- GFP_DMA | GFP_KERNEL);
+ GFP_KERNEL);
if (!buf->virt)
return -ENOMEM;
_
Patches currently in -mm which might be from hebaoquan@kylinos.cn are
reply other threads:[~2026-10-24 8:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20261024085829.3D7DD1F01825@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=harry@kernel.org \
--cc=hch@lst.de \
--cc=hebaoquan@kylinos.cn \
--cc=mm-commits@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.